From: Peter Osterlund <petero2@telia.com>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test8, DEBUG_SLAB, oops in as_latter_request()
Date: 20 Oct 2003 21:37:03 +0200 [thread overview]
Message-ID: <m27k2zpuow.fsf@p4.localdomain> (raw)
In-Reply-To: <3F932B81.2040202@cyberone.com.au>
Nick Piggin <piggin@cyberone.com.au> writes:
> Andrew Morton wrote:
>
> >Peter Osterlund <petero2@telia.com> wrote:
> >
> >>I was running 2.6.0-test8 compiled with CONFIG_DEBUG_SLAB=y. When
> >> testing the CDRW packet writing driver, I got an oops in
> >> as_latter_request. (Full oops at the end of this message.) It is
> >> repeatable and happens because arq->rb_node.rb_right is uninitialized.
> >>
> >
> >deadline seems to have the same problem.
> >
> >We may as well squish this with the big hammer?
> >
>
> Thanks for the report, Peter.
>
> The request is a special request, so either blk_attempt_remerge should
> never be called on it, or blk_attempt_remerge (or as_latter_request) should
> check for this. Its up to Jens.
I don't think it is a special request. I added this debug hack:
--- linux/drivers/block/as-iosched.c~ 2003-10-19 20:33:45.000000000 +0200
+++ linux/drivers/block/as-iosched.c 2003-10-20 21:14:20.000000000 +0200
@@ -1501,9 +1501,18 @@
static struct request *
as_latter_request(request_queue_t *q, struct request *rq)
{
- struct as_rq *arq = RQ_DATA(rq);
- struct rb_node *rbnext = rb_next(&arq->rb_node);
- struct request *ret = NULL;
+ struct as_rq *arq;
+ struct rb_node *rbnext;
+ struct request *ret;
+
+ arq = RQ_DATA(rq);
+ if (arq->rb_node.rb_right == (void*)0x5a5a5a5a) {
+ printk("flags:%lx sector:%ld cmd:%02x %02x %02x %02x\n",
+ rq->flags, rq->sector,
+ rq->cmd[0], rq->cmd[1], rq->cmd[2], rq->cmd[3]);
+ }
+ rbnext = rb_next(&arq->rb_node);
+ ret = NULL;
if (rbnext)
ret = rb_entry_arq(rbnext)->request;
The result was:
flags:50 sector:186920 cmd:28 00 00 00
Unable to handle kernel paging request at virtual address 5a5a5a66
printing eip:
...
Note that:
0x50 == REQ_CMD | REQ_STARTED
0x28 == GPCMD_READ_10
So this looks like a regular read request to me. I'm not sure if this
means that something else is wrong.
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
prev parent reply other threads:[~2003-10-20 19:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-19 19:54 2.6.0-test8, DEBUG_SLAB, oops in as_latter_request() Peter Osterlund
2003-10-19 21:20 ` Andrew Morton
2003-10-20 0:25 ` Nick Piggin
2003-10-20 7:09 ` Jens Axboe
2003-10-20 8:08 ` Nick Piggin
2003-10-20 19:37 ` Peter Osterlund [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=m27k2zpuow.fsf@p4.localdomain \
--to=petero2@telia.com \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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