Linux Manual Pages development
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Jan Kratochvil <jan@jankratochvil.net>
Cc: Florian Weimer <fw@deneb.enyo.de>, linux-man@vger.kernel.org
Subject: Re: [patchv3] pthread_cond_wait and pthread_cond_timedwait can also return EPERM
Date: Fri, 1 Nov 2024 14:16:46 +0100	[thread overview]
Message-ID: <20241101131646.pv4ksngmvj3b4znv@devuan> (raw)
In-Reply-To: <20241101131011.4vvwbww2ls7oqatb@devuan>

[-- Attachment #1: Type: text/plain, Size: 2064 bytes --]

Hi Jan, Florian,

On Fri, Nov 01, 2024 at 02:10:16PM +0100, Alejandro Colomar wrote:
> Hi Jan,
> 
> On Thu, Oct 10, 2024 at 08:39:20PM +0800, Jan Kratochvil wrote:
> > On Thu, 10 Oct 2024 20:25:56 +0800, Florian Weimer wrote:
> > > Indeed, POSIX disallows EINTR for all three wait functions.
> > 
> > Fixed.
> > 
> > 
> > Jan
> > 
> > Signed-off-by: Jan Kratochvil <jan@jankratochvil.net>
> > Reviewed-by: Florian Weimer <fw@deneb.enyo.de>
> 
> Patch applied.  Thank you both!

Sorry, no; I've removed the patch.  It does two things, but I prefer if
you send two patches, each of which changes one thing, and please
provide a more detailed commit message.  Thanks.

Cheers,
Alex

> 
> Have a lovely day!
> Alex
> 
> > diff --git a/man/man3/pthread_cond_init.3 b/man/man3/pthread_cond_init.3
> > index 42e7eac..df1f631 100644
> > --- a/man/man3/pthread_cond_init.3
> > +++ b/man/man3/pthread_cond_init.3
> > @@ -141,22 +141,28 @@ and a non-zero error code on error.
> >  .
> >  .SH ERRORS
> >  \fBpthread_cond_init\fP,
> > -\fBpthread_cond_signal\fP,
> > -\fBpthread_cond_broadcast\fP,
> > -and \fBpthread_cond_wait\fP
> > +\fBpthread_cond_signal\fP
> > +and \fBpthread_cond_broadcast\fP,
> >  never return an error code.
> >  .P
> > +The \fBpthread_cond_wait\fP function returns
> > +the following error codes on error:
> > +.RS
> > +.TP
> > +\fBEPERM\fP
> > +\fBmutex\fP is not locked.
> > +.RE
> > +.P
> >  The \fBpthread_cond_timedwait\fP function returns
> >  the following error codes on error:
> >  .RS
> >  .TP
> > +\fBEPERM\fP
> > +\fBmutex\fP is not locked.
> > +.TP
> >  \fBETIMEDOUT\fP
> >  The condition variable was not signaled
> >  until the timeout specified by \fIabstime\fP.
> > -.TP
> > -\fBEINTR\fP
> > -\fBpthread_cond_timedwait\fP was interrupted by a signal.
> > -.RE
> >  .P
> >  The \fBpthread_cond_destroy\fP function returns
> >  the following error code on error:
> 
> 
> -- 
> <https://www.alejandro-colomar.es/>



-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2024-11-01 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 12:53 [patch] pthread_cond_wait and pthread_cond_timedwait can also return EPERM Jan Kratochvil
2024-10-10 10:32 ` Florian Weimer
2024-10-10 11:46   ` [patch] pthread_cond_wait and pthread_cond_timedwait can also return EPERMignalignal Jan Kratochvil
2024-10-10 12:25     ` Florian Weimer
2024-10-10 12:39       ` [patchv3] pthread_cond_wait and pthread_cond_timedwait can also return EPERM Jan Kratochvil
2024-11-01 13:10         ` Alejandro Colomar
2024-11-01 13:16           ` Alejandro Colomar [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241101131646.pv4ksngmvj3b4znv@devuan \
    --to=alx@kernel.org \
    --cc=fw@deneb.enyo.de \
    --cc=jan@jankratochvil.net \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox