From: Al Viro <viro@ftp.linux.org.uk>
To: Jens Axboe <axboe@suse.de>
Cc: Mark Lord <lkml@rtr.ca>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.16-git4: kernel BUG at block/ll_rw_blk.c:3497
Date: Wed, 29 Mar 2006 09:27:47 +0100 [thread overview]
Message-ID: <20060329082747.GV27946@ftp.linux.org.uk> (raw)
In-Reply-To: <20060329081642.GU8186@suse.de>
On Wed, Mar 29, 2006 at 10:16:43AM +0200, Jens Axboe wrote:
> triggering. What sort of testing were you running, exactly?
>
> Al, any ideas?
I really wonder why it's the call from do_exit() that triggers it.
The thing is, we get off-by-exactly-one here and all previous callers
of that puppy would be elsewhere (cfq, mostly).
IOW, we get exactly one extra call of put_io_context() _and_ have it
happen before do_exit() (i.e. from normal IO paths). Interesting...
Is there any way to reproduce it without too much PITA?
next prev parent reply other threads:[~2006-03-29 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 0:51 2.6.16-git4: kernel BUG at block/ll_rw_blk.c:3497 Mark Lord
2006-03-29 8:16 ` Jens Axboe
2006-03-29 8:27 ` Al Viro [this message]
2006-03-29 9:08 ` Jens Axboe
2006-03-29 13:52 ` Mark Lord
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=20060329082747.GV27946@ftp.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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