From: "Tulio Magno Quites Machado Filho" <tuliom@linux.vnet.ibm.com>
To: Libc-help Mailing List <libc-help@sourceware.org>
Subject: Why is lock elision forbidden in suid?
Date: Thu, 19 Oct 2017 20:11:00 -0000 [thread overview]
Message-ID: <87wp3qaoev.fsf@linux.vnet.ibm.com> (raw)
In a message to libc-alpha from 2013 [1] [2], there has been an agreement
that lock elision should be disabled for suid programs. However, these
messages don't make it clear why it's necessary.
Are there any other reasons beside the risk of adding new code to critical
programs?
[1] https://sourceware.org/ml/libc-alpha/2013-06/msg00561.html
[2] https://sourceware.org/ml/libc-alpha/2013-06/msg00578.html
--
Tulio Magno
next reply other threads:[~2017-10-19 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 20:11 Tulio Magno Quites Machado Filho [this message]
2017-10-19 21:20 ` Carlos O'Donell
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=87wp3qaoev.fsf@linux.vnet.ibm.com \
--to=tuliom@linux.vnet.ibm.com \
--cc=libc-help@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).