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

Message-Id: <1209573069.6433.41.camel@lappy>
Date:	Wed, 30 Apr 2008 18:31:09 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Jeff Moyer <jmoyer@...hat.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	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 Wed, 2008-04-30 at 10:46 -0400, Jeff Moyer wrote:
> Peter Zijlstra <peterz@...radead.org> writes:
> 
> > 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.
> 
> Peter, any update on this?
> 
> FWIW, I've been running the aio-dio-invalidate-failure test on a fedora
> kernel (2.6.25-8.fc9.i686) for several days now without any problems.
> However, I'm not sure I can reproduce the bugs at all.  I'll revert to a
> 2.6.24 kernel and try.

I've ran -git for 10+ hours without crashing, but I've also
changed .config settings (enabled many debugging switches). I'm starting
to work my way backwards to the previous setup that did crash, but since
it takes so long to test each kernel its slow going.



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