linux-kernel - Re: [PATCH] CRED: Holding a spinlock does not imply the holding of RCU read lock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <alpine.LRH.2.00.1004270850050.13362@tundra.namei.org>
Date:	Tue, 27 Apr 2010 08:50:16 +1000 (EST)
From:	James Morris <jmorris@...ei.org>
To:	David Howells <dhowells@...hat.com>
cc:	linux-security-module@...r.kernel.org, serue@...ibm.com,
	paulmck@...ibm.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] CRED: Holding a spinlock does not imply the holding of
 RCU read lock

On Mon, 26 Apr 2010, David Howells wrote:

> From: Serge E. Hallyn <serue@...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@...ibm.com>
> Reviewed-by: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
> Signed-off-by: David Howells <dhowells@...hat.com>


Applied to
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next


-- 
James Morris
<jmorris@...ei.org>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/