linux-kernel - Re: locking hierarchy based on lockdep

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

Date:	Mon, 6 Nov 2006 15:22:33 -0500 (EST)
From:	Jason Baron <jbaron@...hat.com>
To:	Roland Dreier <rdreier@...co.com>
cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	arjan@...radead.org
Subject: Re: locking hierarchy based on lockdep


On Mon, 6 Nov 2006, Roland Dreier wrote:

>  > i like your idea of using lockdep to document locking hierarchies.
> 
> Yes, it's definitely a cool idea.  I think the current implementation
> is not that useful, since it jams all the unrelated kernel locks into
> a single ordered list, when in fact many locks simply have no ordering
> relationship at all because they're never both taken.  This makes the
> list hard to read and in fact loses the information of which locks
> have been taken together.
> 
>  - R.
> 

interesting...perhaps if we layered say the directory structure on the 
list too like by the top level kernel directories drivers, kernel, mm, 
net, etc. it might be more readable.


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