From: Stefan Liebler <stli@linux.ibm.com>
To: libc-stable@sourceware.org
Cc: libc-alpha@sourceware.org, Florian Weimer <fweimer@redhat.com>
Subject: [COMMITTED 2.27 / 2.28] Fix race in pthread_mutex_lock while promoting to PTHREAD_MUTEX_ELISION_NP [BZ #23275]
Date: Mon, 01 Jan 2018 00:00:00 -0000 [thread overview]
Message-ID: <0b9dbba4-26d0-e87d-086c-9705c10ef46c@linux.ibm.com> (raw)
In-Reply-To: <20603cf9-6427-d7da-8bf6-b2eed6abb61a@linux.ibm.com>
On 10/17/2018 12:28 PM, Stefan Liebler wrote:
> On 10/16/2018 03:01 PM, Florian Weimer wrote:
>> * Stefan Liebler:
>>
>>> The flag PTHREAD_MUTEX_NO_ELISION_NP is not explicitly checked before
>>> FORCE_ELISION is called. But only one of those two flags can be set.
>>> Your remaining assumption is correct.
>>> I've changed the comment in the three force-elision.h files. Is this
>>> okay?
>>
>> The comment looks good to me know. Thanks!
>>
>> Florian
>>
> Committed, bugzilla closed and target milestone is set to 2.29.
>
> Thanks,
> Stefan
>
Starting with glibc 2.27, the configure switch --enable-lock-elision was
removed with commit "Add elision tunables"
(https://sourceware.org/git/?p=glibc.git;a=commit;h=07ed18d26a342741cb25a4739158c65ed9dd4d09).
Now you can use lock-elision by just setting the tunables environment
variable.
Therefore I've cherry picked this patch to release branch 2.27 / 2.28.
Bye
Stefan
next parent reply other threads:[~2018-10-18 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f3fc33e5-aa98-f772-a1bf-c02ddf9352c7@linux.ibm.com>
[not found] ` <a10e9a65-5031-fe9c-8552-3f046c351be6@redhat.com>
[not found] ` <ebac7b01-c4ff-4310-d7cc-748c1499731a@linux.ibm.com>
[not found] ` <874ldm3v09.fsf@oldenburg.str.redhat.com>
[not found] ` <20603cf9-6427-d7da-8bf6-b2eed6abb61a@linux.ibm.com>
2018-01-01 0:00 ` Stefan Liebler [this message]
2021-10-01 14:19 libc-stable&sourceware 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=0b9dbba4-26d0-e87d-086c-9705c10ef46c@linux.ibm.com \
--to=stli@linux.ibm.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-stable@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).