linux-kernel - Re: AIO/DIO lockup/crash

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1209404909.13978.23.camel@twins>
Date:	Mon, 28 Apr 2008 19:48:29 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-aio <linux-aio@...ck.org>,
	Zach Brown <zach.brown@...cle.com>,
	Clark Williams <williams@...hat.com>
Subject: Re: AIO/DIO lockup/crash

On Mon, 2008-04-28 at 09:08 -0700, Andrew Morton wrote:

> erk, that's dio->bio_lock, isn't it?

Yep.

> That lock is super-simple and hasn't changed in quite some time.  If there
> has been major memory wreckage and we're simply grabbing at a "lock" in
> random memory then I'd expect the bug to maninfest in different ways on
> different runs?

Looks like it.

> I assume you have lots of runtime debugging options enabled.

Not on this particular run. I'll start a -git run this evening with most
of the debugging option enabled. It takes a few hours to reproduce, so I
let it run over-night.

--
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/