signal(7): why does it say that pthread_mutex_lock() and thread_cond_wait() can fail with EINTR?

[Alejandro Colomar]

Hi Florian, Arkadiusz,

On Thu, Jan 02, 2025 at 10:53:57AM +0100, Florian Weimer wrote:
> * Alejandro Colomar:
> 
> >> The underlying futex() call indeed fails with EINTR but it's called
> >> again by both glibc and musl.
> >
> > I've CCed glibc, in case they can comment.  Maybe this behavior changed
> > at some point in the past?  I don't know.
> 
> Maybe in the LinuxThreads implementation.  I think NPTL has handled this
> correctly from the beginning.  POSIX bans the EINTR failure condition.

Thanks!

Arkadiusz, would you do the honours writing a patch?  Should I?

Have a lovely new year!
Alex

> 
> Thanks,
> Florian
> 

-- 
<https://www.alejandro-colomar.es/>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <https://sourceware.org/pipermail/libc-help/attachments/20250102/eeead6ee/attachment.sig>