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/19193] New: pthread_kill returns ESRCH for a thread ID whose lifetime has not ended Date: Sat, 31 Oct 2015 11:42:00 -0000 [thread overview] Message-ID: <bug-19193-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=19193 Bug ID: 19193 Summary: pthread_kill returns ESRCH for a thread ID whose lifetime has not ended Product: glibc Version: 2.23 Status: NEW Severity: normal Priority: P2 Component: nptl Assignee: unassigned at sourceware dot org Reporter: fweimer at redhat dot com CC: drepper.fsp at gmail dot com Target Milestone: --- Flags: security- POSIX specifies that the lifetime of a thread ID ends when it terminates and it is detached or joined (or immediately at creation when it is created already detached). POSIX does not specify the ESRCH return value for pthread_kill in case the thread has exited, only if the lifetime of the thread ID has ended (as an option). In analogy with the specification of kill and process lifetime, threads which have exited should not cause pthread_kill to return ESRCH. I think pthread_kill has to ignore the ESRCH error from the system call. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2015-10-31 11:42 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-31 11:42 fweimer at redhat dot com [this message] 2021-08-17 6:23 ` [Bug nptl/19193] " fweimer at redhat dot com 2021-08-17 6:25 ` fweimer at redhat dot com 2021-08-17 12:01 ` fweimer at redhat dot com 2021-08-17 12:01 ` fweimer at redhat dot com 2021-08-17 12:01 ` [Bug nptl/19193] pthread_kill, pthread_cancel return " fweimer at redhat dot com 2021-08-17 12:45 ` fweimer at redhat dot com 2021-08-17 13:52 ` fweimer at redhat dot com 2021-09-13 10:46 ` fweimer at redhat dot com 2021-09-17 11:29 ` fweimer at redhat dot com 2021-09-20 12:58 ` cvs-commit at gcc dot gnu.org 2021-09-20 13:49 ` cvs-commit at gcc dot gnu.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-19193-131@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).