lkml.org 
[lkml]   [2011]   [Jun]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [tip:sched/urgent] lockdep: Fix lock_is_held() on recursion

* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:

> On Tue, 2011-06-07 at 12:02 +0000, tip-bot for Peter Zijlstra wrote:
> > Commit-ID: f2513cde93f0957d5dc6c09bc24b0cccd27d8e1d
> > Gitweb: http://git.kernel.org/tip/f2513cde93f0957d5dc6c09bc24b0cccd27d8e1d
> > Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > AuthorDate: Mon, 6 Jun 2011 12:32:43 +0200
> > Committer: Ingo Molnar <mingo@elte.hu>
> > CommitDate: Tue, 7 Jun 2011 12:25:50 +0200
> >
> > lockdep: Fix lock_is_held() on recursion
> >
> > The main lock_is_held() user is lockdep_assert_held(), avoid false
> > assertions in lockdep_off() sections by unconditionally reporting the
> > lock is taken.
> >
> > [ the reason this is important is a lockdep_assert_held() in ttwu()
> > which triggers a warning under lockdep_off() as in printk() which
> > can trigger another wakeup and lock up due to spinlock
> > recursion, as reported and heroically debugged by Arne Jansen ]
> >
> > Reported-and-tested-by: Arne Jansen <lists@die-jansens.de>
> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> > Cc: Linus Torvalds <torvalds@linux-foundation.org>
> > Cc: <stable@kernel.org>
>
> Not _that_ critical for stable since the offending lockdep_assert_held()
> doesn't exist in .39, still definitely won't hurt.

Correct, the bug was hard enough to find, i didnt want someone else
to trigger a similar one. There's numerous lockdep_assert_held()
instances all around the tree.

Thanks,

Ingo


\
 
 \ /
  Last update: 2011-06-07 20:09    [W:0.059 / U:0.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site