From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-aio <linux-aio@kvack.org>,
Zach Brown <zach.brown@oracle.com>,
Clark Williams <williams@redhat.com>
Subject: Re: AIO/DIO lockup/crash
Date: Mon, 28 Apr 2008 19:48:29 +0200 [thread overview]
Message-ID: <1209404909.13978.23.camel@twins> (raw)
In-Reply-To: <20080428090857.beb19a20.akpm@linux-foundation.org>
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.
next prev parent reply other threads:[~2008-04-28 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-28 12:29 AIO/DIO lockup/crash Peter Zijlstra
2008-04-28 16:08 ` Andrew Morton
2008-04-28 17:48 ` Peter Zijlstra [this message]
2008-04-30 14:46 ` Jeff Moyer
2008-04-30 16:31 ` Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1209404909.13978.23.camel@twins \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=williams@redhat.com \
--cc=zach.brown@oracle.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox