public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: Lorenzo Allegrucci <l_allegrucci@despammed.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.6-mm5 oops mounting ext3 or reiserfs with -o barrier
Date: Sat, 22 May 2004 23:30:18 +0200	[thread overview]
Message-ID: <20040522213018.GA31224@suse.de> (raw)
In-Reply-To: <20040522212028.GA31188@suse.de>

On Sat, May 22 2004, Jens Axboe wrote:
> On Sat, May 22 2004, Andrew Morton wrote:
> > Lorenzo Allegrucci <l_allegrucci@despammed.com> wrote:
> > >
> > > 
> > > I get a 100% reproducible oops mounting an ext3 or reiserfs
> > > partition with -o barrier enabled.
> > > Hand written oops (for ext3):
> > 
> > That's a lot of hand-writing.  Thanks for doing that.  You can usually omit
> > the hex numbers in [brackets] when doing this.
> > 
> > The crash is here:
> > 
> > static inline void blkdev_dequeue_request(struct request *req)
> > {
> > 	BUG_ON(list_empty(&req->queuelist));
> > 
> > perhaps related to that I/O error sending the code through less-tested
> > paths.
> 
> Ouch indeed, I'll get that fixed up first thing in the morning.

Can you test this work-around? The work-around should be perfectly safe,
this is just a case where a BUG_ON() does more harm than good :-)

--- drivers/ide/ide-io.c~	2004-05-21 11:02:58.000000000 +0200
+++ drivers/ide/ide-io.c	2004-05-22 23:28:37.692944185 +0200
@@ -291,6 +291,8 @@
 		sector = real_rq->hard_sector;
 
 	bad_sectors = real_rq->hard_nr_sectors - good_sectors;
+	/* work-around, make sure request is on queue */
+	elv_requeue_request(drive->queue, real_rq);
 	if (good_sectors)
 		__ide_end_request(drive, real_rq, 1, good_sectors);
 	if (bad_sectors)

-- 
Jens Axboe


  reply	other threads:[~2004-05-22 21:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-22 19:07 2.6.6-mm5 oops mounting ext3 or reiserfs with -o barrier Lorenzo Allegrucci
2004-05-22 19:21 ` Andrew Morton
2004-05-22 21:20   ` Jens Axboe
2004-05-22 21:30     ` Jens Axboe [this message]
2004-05-23  8:58       ` Lorenzo Allegrucci
2004-05-23  9:11         ` Jens Axboe
2004-05-23 10:03           ` Jens Axboe
2004-05-23 15:32             ` Lorenzo Allegrucci
2004-05-23 15:45               ` Jens Axboe
2004-05-23 16:43                 ` Lorenzo Allegrucci
2004-05-23 16:56                   ` Jens Axboe
2004-05-23 17:17                     ` Lorenzo Allegrucci
2004-05-23 17:31                       ` Jens Axboe
2004-05-23 20:41                         ` Lorenzo Allegrucci
2004-05-23  8:27 ` Jens Axboe
2004-05-23 10:37   ` Kurt Garloff
2004-05-23 10:56     ` Jens Axboe

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=20040522213018.GA31224@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@osdl.org \
    --cc=l_allegrucci@despammed.com \
    --cc=linux-kernel@vger.kernel.org \
    /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