From: David Miller <davem@davemloft.net>
To: jens.axboe@oracle.com
Cc: fujita.tomonori@lab.ntt.co.jp, linux-kernel@vger.kernel.org
Subject: IDE crash...
Date: Mon, 22 Oct 2007 23:50:10 -0700 (PDT) [thread overview]
Message-ID: <20071022.235010.59469063.davem@davemloft.net> (raw)
I'm debugging a blk_rq_map_sg() crash that i'm getting on sparc64 as
root is mounted over IDE. I think I know what is happening now.
The IDE sg table is allocated and initialized like this in
drivers/ide/ide-probe.c:
x = kmalloc(sizeof(struct scatterlist) * nents, GFP_XXX);
sg_init_table(x, nents);
So far, so good.
Now, ide_map_sg() passes requests down to blk_rq_map_sg() like this in
drivers/block/ide-io.c:
hwif->sg_nents = blk_rq_map_sg(drive->queue, rq, sg);
Ok, so what does blk_rq_map_sg() do?
sg = NULL;
rq_for_each_segment(bvec, rq, iter) {
...
if (bvprv && cluster) {
...
} else {
new_segment:
if (!sg)
sg = sglist;
else
sg = sg_next(sg);
...
}
bvprv = bvec;
} /* segments in rq */
if (sg)
__sg_mark_end(sg);
So let's say the first request comes in and needs 2 segs.
This will mark sg[1].page_link with 0x2
If the next request from IDE needs 4 segs, we'll OOPS because
sg_next() on &sg[1] will see page_link bit 0x2 is set and
therefore return NULL.
A quick look shows that if you're testing on SCSI (or something
layered on top of it like SATA or PATA) you won't see this seemingly
guarenteed crash because the SCSI mid-layer allocates a fresh sglist
via mempool_alloc() and runs sg_init_table() on it for every I/O
request.
next reply other threads:[~2007-10-23 6:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 6:50 David Miller [this message]
2007-10-23 7:02 ` Jens Axboe
2007-10-23 7:09 ` Jens Axboe
2007-10-23 7:14 ` FUJITA Tomonori
2007-10-23 7:23 ` Jens Axboe
2007-10-23 7:18 ` David Miller
2007-10-23 7:23 ` Jens Axboe
2007-10-23 7:43 ` David Miller
2007-10-23 7:45 ` Jens Axboe
2007-10-23 15:10 ` John Stoffel
2007-10-24 6:49 ` Jens Axboe
2007-10-24 16:27 ` John Stoffel
2007-10-24 18:10 ` Jens Axboe
2007-10-23 10:52 ` FUJITA Tomonori
2007-10-23 10:57 ` Jens Axboe
2007-10-23 10:58 ` Jens Axboe
2007-10-23 11:10 ` FUJITA Tomonori
2007-10-23 11:43 ` Jens Axboe
2007-10-23 21:18 ` David Miller
2007-10-23 21:44 ` 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=20071022.235010.59469063.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=jens.axboe@oracle.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
Powered by JetHome