linux-kernel - Re: kernel BUG at drivers/md/raid5.c:693!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20131126094250.GH10022@twins.programming.kicks-ass.net>
Date:	Tue, 26 Nov 2013 10:42:50 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	NeilBrown <neilb@...e.de>
Cc:	fengguang.wu@...el.com, "Li, Shaohua" <shaohua.li@...el.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>
Subject: Re: kernel BUG at drivers/md/raid5.c:693!

On Tue, Nov 26, 2013 at 03:31:06PM +1100, NeilBrown wrote:
> The stack trace in the previous email seemed to suggest that a process was
> blocking inside a wake_up call, but it wasn't at all conclusive.  And I've
> seen a few wake_ups in other stack traces which seem to be connected with
> other deadlock.  Probably some sort of co-incidence.

It appears stuck in some paravirt clock layer.. or just a lucky hit.

I never run on (para)virt if I can help it, so I'm not much help there.
--
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/