From: "Serge E. Hallyn" <serue@us.ibm.com>
To: David Howells <dhowells@redhat.com>,
"Paul E. McKenney" <paulmck@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Documentation/credentials.txt
Date: Fri, 23 Apr 2010 18:55:33 -0500 [thread overview]
Message-ID: <20100423235532.GA17804@us.ibm.com> (raw)
Hi,
In the section 'ACCESSING ANOTHER TASK'S CREDENTIALS', the file
Documentation/credentials.txt says:
> A function need not get RCU read lock to use __task_cred() if it is holding a
> spinlock at the time as this implicitly holds the RCU read lock.
AIUI, that is not actually right any more, is it? A spinlock does not
suffice as it does not necessarily imply an RCU read-side critical section
(anymore). Of course the spinlock specifically protecting updates would
suffice, but that's not what this is saying.
Am I way off base?
thanks,
-serge
next reply other threads:[~2010-04-23 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 23:55 Serge E. Hallyn [this message]
2010-04-24 0:14 ` Documentation/credentials.txt Paul E. McKenney
2010-04-24 0:46 ` Documentation/credentials.txt Serge E. Hallyn
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=20100423235532.GA17804@us.ibm.com \
--to=serue@us.ibm.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.com \
/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