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/12889] Race condition in pthread_kill
Date: Mon, 13 Sep 2021 10:46:03 +0000 [thread overview]
Message-ID: <bug-12889-131-J49CBUyYbq@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12889-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=12889
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |2.35
--- Comment #8 from Florian Weimer <fweimer at redhat dot com> ---
Fixed for 2.35 via:
commit 526c3cf11ee9367344b6b15d669e4c3cb461a2be
Author: Florian Weimer <fweimer@redhat.com>
Date: Mon Sep 13 11:06:08 2021 +0200
nptl: Fix race between pthread_kill and thread exit (bug 12889)
A new thread exit lock and flag are introduced. They are used to
detect that the thread is about to exit or has exited in
__pthread_kill_internal, and the signal is not sent in this case.
The test sysdeps/pthread/tst-pthread_cancel-select-loop.c is derived
from a downstream test originally written by Marek Polacek.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-09-13 10:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 0:39 [Bug nptl/12889] New: " bugdal at aerifal dot cx
2011-06-18 23:35 ` [Bug nptl/12889] " ppluzhnikov at google dot com
2012-04-29 3:04 ` bugdal at aerifal dot cx
2014-06-27 13:11 ` fweimer at redhat dot com
2015-10-31 12:08 ` fweimer at redhat dot com
2015-10-31 12:37 ` schwab@linux-m68k.org
2015-10-31 20:27 ` bugdal at aerifal dot cx
2021-08-17 6:25 ` fweimer at redhat dot com
2021-08-17 12:01 ` fweimer at redhat dot com
2021-08-17 12:44 ` fweimer at redhat dot com
2021-08-17 13:52 ` fweimer at redhat dot com
2021-09-13 10:41 ` cvs-commit at gcc dot gnu.org
2021-09-13 10:46 ` fweimer at redhat dot com [this message]
2021-09-13 12:20 ` cvs-commit at gcc dot gnu.org
2021-09-21 13:05 ` fweimer at redhat dot com
2021-09-23 8:54 ` cvs-commit at gcc dot gnu.org
2021-09-23 9:04 ` 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-12889-131-J49CBUyYbq@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).