Messages in this thread | | | Date | Tue, 5 Aug 2008 00:14:48 +0300 | From | "Pekka Enberg" <> | 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@qumranet.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.
| |