public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug nptl/29029] poll() spuriously returns EINTR during thread cancellation and with cancellation disabled Date: Wed, 06 Apr 2022 13:31:57 +0000 [thread overview] Message-ID: <bug-29029-131-PhNNx5EJqY@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29029-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29029 --- Comment #3 from Florian Weimer <fweimer at redhat dot com> --- Well, I spoke to soon, it's actually documented in signal(7): “ The following interfaces are never restarted after being interrupted by a signal handler, regardless of the use of SA_RESTART; they always fail with the error EINTR when interrupted by a signal handler: ” <https://man7.org/linux/man-pages/man7/signal.7.html> I think that explains why glibc used the old, more complex code: it may be required for POSIX conformance. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-04-06 13:31 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-04-05 21:32 [Bug nptl/29029] New: " aurelien at aurel32 dot net 2022-04-05 22:28 ` [Bug nptl/29029] " adhemerval.zanella at linaro dot org 2022-04-06 13:27 ` fweimer at redhat dot com 2022-04-06 13:31 ` fweimer at redhat dot com [this message] 2022-04-06 14:38 ` adhemerval.zanella at linaro dot org 2022-04-06 14:41 ` fweimer at redhat dot com 2022-04-06 14:46 ` adhemerval.zanella at linaro dot org 2022-04-06 15:28 ` adhemerval.zanella at linaro dot org 2022-04-14 18:43 ` adhemerval.zanella at linaro dot org 2023-06-21 3:00 ` andres at anarazel dot de 2023-06-21 14:25 ` adhemerval.zanella at linaro dot org
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=bug-29029-131-PhNNx5EJqY@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).