[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1192520804.27435.88.camel@twins>
Date: Tue, 16 Oct 2007 09:46:44 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [git pull] lockdep for v2.6.24
On Mon, 2007-10-15 at 18:14 -0700, Linus Torvalds wrote:
>
> On Mon, 15 Oct 2007, Peter Zijlstra wrote:
> >
> > please pull the lockdep tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/peterz/linux-2.6-lockdep.git v2.6.24-lockdep
>
> Hmm. I'm now getting
>
> WARNING: at kernel/lockdep.c:700 look_up_lock_class()
>
> Call Trace:
> [<ffffffff8105562a>] __lock_acquire+0x15f/0xc92
> [<ffffffff810a5804>] do_lookup+0x83/0x1b0
> [<ffffffff8105654a>] lock_acquire+0x5a/0x73
> [<ffffffff810a5804>] do_lookup+0x83/0x1b0
> [<ffffffff81052b59>] debug_mutex_lock_common+0x16/0x23
> [<ffffffff81347d26>] mutex_lock_nested+0x10c/0x2b0
> [<ffffffff810a5804>] do_lookup+0x83/0x1b0
> [<ffffffff810a7b89>] __link_path_walk+0x924/0xde9
> [<ffffffff810a80a6>] link_path_walk+0x58/0xe0
> [<ffffffff81348ef6>] _spin_unlock+0x17/0x20
> [<ffffffff8109cc31>] get_unused_fd_flags+0x115/0x126
> [<ffffffff810a8432>] do_path_lookup+0x1ae/0x229
> [<ffffffff810a8e3d>] __path_lookup_intent_open+0x56/0x96
> [<ffffffff810a8fe0>] open_namei+0x7d/0x66c
> [<ffffffff8109ce9f>] do_filp_open+0x1c/0x38
> [<ffffffff81348ef6>] _spin_unlock+0x17/0x20
> [<ffffffff8109cc31>] get_unused_fd_flags+0x115/0x126
> [<ffffffff8109cf01>] do_sys_open+0x46/0xc3
> [<ffffffff8100bc3e>] system_call+0x7e/0x83
>
> which seems to be new..
Yeah, Ingo just told me about that too :-(
Seems I dropped a patch in my test runs.. Anyway, pushed a fix into the
above tree.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists