[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020808041414x2c1c8b82n5939b82e9a2ca99d@mail.gmail.com>
Date: Tue, 5 Aug 2008 00:14:48 +0300
From: "Pekka Enberg" <penberg@...helsinki.fi>
To: "Andrea Arcangeli" <andrea@...ranet.com>
Cc: "Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
"Dave Jones" <davej@...hat.com>,
"Roland Dreier" <rdreier@...co.com>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"David Miller" <davem@...emloft.net>, jeremy@...p.org,
hugh@...itas.com, mingo@...e.hu, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, arjan <arjan@...radead.org>
Subject: Re: [PATCH] workaround minor lockdep bug triggered by mm_take_all_locks
Hi Andrea,
On Mon, Aug 04, 2008 at 10:37:22PM +0200, Peter Zijlstra wrote:
>> You're so wrong it not even funny. It reports about deadlocks before
>> they happen. All it needs is to observe a lock order violation and it
On Tue, Aug 5, 2008 at 12:09 AM, Andrea Arcangeli <andrea@...ranet.com> wrote:
> Now tell me how it helps to report them... It tells me the system has
> crashed and where, it's not like I couldn't figure it out by myself
> but just noticing nothing works and all cpus are spinning in some
> spinlock slow path and pressing sysrq+t/p.
Sometimes it's hard to actually trigger a deadlock condition during
development, especially if you're not developing on a big iron
machine.
--
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