[lkml]   [2006]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: lockdep oddity

* Ingo Molnar <> wrote:

> * Ingo Molnar <> wrote:
> > > The reason is that the BUILD_LOCK_OPS macros in kernel/lockdep.c
> > > don't contain any of the *_acquire calls, while all of the _unlock
> > > functions contain a *_release call. Hence I get immediately
> > > unbalanced locks.
> >
> > hmmm ... that sounds like a bug. Weird - i recently ran
> > PREEMPT+SMP+LOCKDEP kernels and didnt notice this.
> ok, the reason i didnt find this problem is because this is fixed in
> my tree, but i didnt realize that it's a fix also for upstream ...

actually ... it works fine in the upstream kernel due to this:

* If lockdep is enabled then we use the non-preemption spin-ops
* even on CONFIG_PREEMPT, because lockdep assumes that interrupts are
* not re-enabled during lock-acquire (which the preempt-spin-ops do):
#if !defined(CONFIG_PREEMPT) || !defined(CONFIG_SMP) || \

so i'm wondering, how did you you manage to get into the
BUILD_LOCK_OPS() branch?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-09-05 21:49    [W:0.142 / U:13.708 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site