public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>, Tejun Heo <tj@kernel.org>
Subject: Re: [sporadic crash] blk: request botched
Date: Tue, 29 Mar 2011 13:38:34 +0200	[thread overview]
Message-ID: <4D91C4BA.9030502@fusionio.com> (raw)
In-Reply-To: <20110329111755.GA1760@elte.hu>

On 2011-03-29 13:17, Ingo Molnar wrote:
> 
> FYI, i'm seeing a new block IO related boot failure. It starts by the kernel spewing:
> 
>  [   84.434778] blk: request botched
>  [   84.437546] blk: request botched
>  [   84.441532] blk: request botched
> 
> And after more dying noises, a colorful kernel crash in an apparently rarely
> excercised error handler:

I don't think it's the error handler being broken, it simply looks like
a request that is in a bad bad state thus causing the normal rq -> bio
-> bvec run through to bomb out.

So the 'request botched' is the real BUG here.

Is that part reproducible? If so, can you please try with this patch?

diff --git a/block/blk-core.c b/block/blk-core.c
index e0a0623..3045d0e 100644
--- a/block/blk-core.c
+++ b/block/blk-core.c
@@ -2163,7 +2163,8 @@ bool blk_update_request(struct request *req, int error, unsigned int nr_bytes)
 	 * size, something has gone terribly wrong.
 	 */
 	if (blk_rq_bytes(req) < blk_rq_cur_bytes(req)) {
-		printk(KERN_ERR "blk: request botched\n");
+		blk_dump_rq_flags(req, "request botched");
+		WARN_ON(1);
 		req->__data_len = blk_rq_cur_bytes(req);
 	}
 

-- 
Jens Axboe


      reply	other threads:[~2011-03-29 11:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 18:56 [GIT PULL] block drivers for 2.6.39-rc Jens Axboe
2011-03-28  4:23 ` Ingo Molnar
2011-03-28  4:37   ` Linus Torvalds
2011-03-28  4:43     ` Ingo Molnar
2011-03-28  5:08     ` Stephen Rothwell
2011-03-28  6:43       ` Jens Axboe
2011-03-28  7:04         ` Stephen Rothwell
2011-03-28  7:21           ` Jens Axboe
2011-03-28 23:06 ` Linus Torvalds
2011-03-29  6:34   ` Jens Axboe
2011-03-29 13:18     ` scameron
2011-03-29 11:17 ` [sporadic crash] blk: request botched Ingo Molnar
2011-03-29 11:38   ` Jens Axboe [this message]

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=4D91C4BA.9030502@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=torvalds@linux-foundation.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