linux-kernel - Documentation/credentials.txt

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-next>] [day] [month] [year] [list]

Message-ID: <20100423235532.GA17804@us.ibm.com>
Date:	Fri, 23 Apr 2010 18:55:33 -0500
From:	"Serge E. Hallyn" <serue@...ibm.com>
To:	David Howells <dhowells@...hat.com>,
	"Paul E. McKenney" <paulmck@...ibm.com>
Cc:	lkml <linux-kernel@...r.kernel.org>
Subject: Documentation/credentials.txt

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
--
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/