linux-kernel - Re: [PATCH] lockdep: Include all lock classes in all_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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1202052062.32654.69.camel@lappy>
Date:	Sun, 03 Feb 2008 16:21:02 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Dale Farnsworth <dale@...nsworth.org>
Cc:	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] lockdep: Include all lock classes in all_lock_classes


On Fri, 2008-02-01 at 08:21 -0700, Dale Farnsworth wrote:
> Add each lock class to the all_lock_classes list when it is
> first registered.
> 
> Previously, lock classes were added to all_lock_classes when
> the lock class was first used. 

> Since one of the uses of the list is to find unused locks, this didn't
> work well.

You mean in lockdep_proc.c to generate the statistics?

Another potential issue might be count_matching_names() generating a
wrong class version.



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