| Date | Thu, 25 Apr 2019 16:01:10 +0200 | From | Peter Zijlstra <> | 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().
|