linux-kernel - Re: [PATCH 02/28] locking/lockdep: Add description and explanation in lockdep design doc

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20190425140110.GS12232@hirez.programming.kicks-ass.net>
Date:   Thu, 25 Apr 2019 16:01:10 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Yuyang Du <duyuyang@...il.com>
Cc:     will.deacon@....com, mingo@...nel.org, bvanassche@....org,
        ming.lei@...hat.com, frederic@...nel.org, tglx@...utronix.de,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 02/28] locking/lockdep: Add description and explanation
 in lockdep design doc

On Wed, Apr 24, 2019 at 06:19:08PM +0800, Yuyang Du wrote:
> +Unlike a lock instance, a lock-class itself never goes away: when a
> +lock-class's instance is used for the first time after bootup the class gets
> +registered, and all (subsequent) instances of that lock-class will be mapped
> +to the lock-class.

That's not entirely accurate anymore. Bart van Assche recently added
lockdep_{,un}register_key().