Thread (6 messages) 6 messages, 3 authors, 2025-01-03

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

From: Alejandro Colomar <alx@kernel.org>
Date: 2025-01-02 12:13:42

Hi Florian, Arkadiusz,

On Thu, Jan 02, 2025 at 10:53:57AM +0100, Florian Weimer wrote:
* Alejandro Colomar:
quoted
quoted
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/>

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help