From: malteskarupke@fastmail.fm
To: libc-alpha@sourceware.org
Subject: [PATCH v3 0/6] nptl: Fix pthread_cond_signal missing a sleeper
Date: Thu, 6 Oct 2022 17:43:23 -0400 [thread overview]
Message-ID: <20221006214329.1084244-1-malteskarupke@fastmail.fm> (raw)
The first patch in this series fixes BZ 25847, the remaining patches
do follow-up clean-up work.
-- New in v3:
Fixed that the first patch didn't work on its own. It had a bug that
was fixed in the third patch in the series. Now the series can be
partially applied and it's fine to stop after any patch.
Also rebased the patches to work on top of 2.36/master
-- New in v2:
The first patch now has the calls at the end of pthread_cond_wait in
the right order.
The third patch now clears the wake-request flag correctly, removing a
case where a waiter could write to a condvar after it was destroyed.
The fifth patch now renames wrefs to crefs.
I also updated comments as requested.
Finally I added another patch because I realized that g1_start was too
complex for its reduced role after signal stealing was no longer
possible, so the final patch cleans that up.
next reply other threads:[~2022-10-06 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 21:43 malteskarupke [this message]
2022-10-06 21:43 ` [PATCH v3 1/6] nptl: Fix pthread_cond_signal missing a sleeper (#BZ 25847) malteskarupke
2022-10-06 21:43 ` [PATCH v3 2/6] nptl: Remove the signal-stealing code. It is no longer needed malteskarupke
2022-10-06 21:43 ` [PATCH v3 3/6] nptl: Optimization by not incrementing wrefs in pthread_cond_wait malteskarupke
2022-10-06 21:43 ` [PATCH v3 4/6] nptl: Make test-cond-printers check the number of waiters malteskarupke
2022-10-06 21:43 ` [PATCH v3 5/6] nptl: Rename __wrefs to __crefs because its meaning has changed malteskarupke
2022-10-06 21:43 ` [PATCH v3 6/6] nptl: Cleaning up __g1_start and related code in pthread_cond_wait malteskarupke
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=20221006214329.1084244-1-malteskarupke@fastmail.fm \
--to=malteskarupke@fastmail.fm \
--cc=libc-alpha@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).