From: James Morris <jmorris@namei.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-security-module@vger.kernel.org, serue@us.ibm.com,
paulmck@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CRED: Holding a spinlock does not imply the holding of RCU read lock
Date: Tue, 27 Apr 2010 08:50:16 +1000 (EST) [thread overview]
Message-ID: <alpine.LRH.2.00.1004270850050.13362@tundra.namei.org> (raw)
In-Reply-To: <20100426105849.26489.72831.stgit@warthog.procyon.org.uk>
On Mon, 26 Apr 2010, David Howells wrote:
> From: Serge E. Hallyn <serue@us.ibm.com>
>
> Change the credentials documentation to make it clear that the RCU read lock
> must be explicitly held when accessing credentials pointers in some other task
> than current. Holding a spinlock does not implicitly hold the RCU read lock.
>
> Signed-off-by: Serge Hallyn <serue@us.ibm.com>
> Reviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> Signed-off-by: David Howells <dhowells@redhat.com>
Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next
--
James Morris
<jmorris@namei.org>
prev parent reply other threads:[~2010-04-26 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 10:58 David Howells
2010-04-26 22:50 ` James Morris [this message]
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=alpine.LRH.2.00.1004270850050.13362@tundra.namei.org \
--to=jmorris@namei.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paulmck@us.ibm.com \
--cc=serue@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
all inboxes | Powered by JetHome®