[lkml]   [2016]   [Feb]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: + kernel-locking-lockdepc-make-lockdep-initialize-itself-on-demand.patch added to -mm tree

* Andrew Morton <> wrote:

> > and it should happen in a well defined place, not be opportunistic (and
> > relatively random) like this, making it dependent on config options and
> > calling contexts.
> That's an unusable assertion, sorry.
> Initializing lockdep in the above manner guarantees that it is initialized
> before it is used. It is *much* more reliable than "try to initialize it before
> some piece of code which hasn't even been written yet tries to take a lock".

So I didn't like that patch because it called into lockdep in a messy way, without
having any real knowledge about whether it's safe to do. Should lockdep ever grow
more complex initialization, such a solution could break in subtle ways. I prefer
clearly broken code with static dependencies over context-dependent broken code
with dynamic call ordering/dependencies.

Fortunately we don't have to apply the patch:

> The conceptual problem is that if some piece of code does spin_lock_init() or
> DEFINE_SPINLOCK(), that lock isn't necessarily initialized yet.

The conceptual problem is that the data structures are not build time initialized
- but the hlist conversion patch solves that problem nicely!

So I'm a happy camper.



 \ /
  Last update: 2016-02-09 12:41    [W:0.203 / U:0.912 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site