From: Jens Axboe <axboe@suse.de>
To: Larry Sendlosky <Larry.Sendlosky@storigen.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-pre3 kernel crash
Date: Tue, 28 Jan 2003 23:06:07 +0100 [thread overview]
Message-ID: <20030128220607.GF31566@suse.de> (raw)
In-Reply-To: <7BFCE5F1EF28D64198522688F5449D5A03C0FA@xchangeserver2.storigen.com>
On Tue, Jan 28 2003, Larry Sendlosky wrote:
> I was glad to see the physical page support in 2.4.20.
> (and also noticed that the current BK tree clobbered it
> on a patch set from Alan).
>
> One question,
>
> + lastdataend = bh_phys(bh) + bh->b_size;
>
> bh_phys(x) uses bh->b_page. Does it make a difference
> if bh->b_page is zero? What if someone combines virt and phys
> buffer addresses in bh list?
Yes good catch! New version attached.
===== drivers/ide/ide-dma.c 1.7 vs edited =====
--- 1.7/drivers/ide/ide-dma.c Wed Nov 20 18:46:24 2002
+++ edited/drivers/ide/ide-dma.c Tue Jan 28 23:04:32 2003
@@ -249,6 +249,7 @@
{
struct buffer_head *bh;
struct scatterlist *sg = hwif->sg_table;
+ unsigned long lastdataend = ~0UL;
int nents = 0;
if (hwif->sg_dma_active)
@@ -256,24 +257,42 @@
bh = rq->bh;
do {
- unsigned char *virt_addr = bh->b_data;
- unsigned int size = bh->b_size;
+ int contig = 0;
+
+ if (bh->b_page) {
+ if (bh_phys(bh) == lastdataend)
+ contig = 1;
+ } else {
+ if ((unsigned long) bh->b_data == lastdataend)
+ contig = 1;
+ }
+
+ if (contig) {
+ sg[nents - 1].length += bh->b_size;
+ lastdataend += bh->b_size;
+ continue;
+ }
if (nents >= PRD_ENTRIES)
return 0;
- while ((bh = bh->b_reqnext) != NULL) {
- if ((virt_addr + size) != (unsigned char *) bh->b_data)
- break;
- size += bh->b_size;
- }
memset(&sg[nents], 0, sizeof(*sg));
- sg[nents].address = virt_addr;
- sg[nents].length = size;
- if(size == 0)
- BUG();
+
+ if (bh->b_page) {
+ sg[nents].page = bh->b_page;
+ sg[nents].offset = bh_offset(bh);
+ lastdataend = bh_phys(bh) + bh->b_size;
+ } else {
+ if ((unsigned long) bh->b_data < PAGE_SIZE)
+ BUG();
+
+ sg[nents].address = bh->b_data;
+ lastdataend = (unsigned long) bh->b_data + bh->b_size;
+ }
+
+ sg[nents].length = bh->b_size;
nents++;
- } while (bh != NULL);
+ } while ((bh = bh->b_reqnext) != NULL);
if(nents == 0)
BUG();
--
Jens Axboe
next prev parent reply other threads:[~2003-01-28 21:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 16:41 2.4.21-pre3 kernel crash Larry Sendlosky
2003-01-28 22:06 ` Jens Axboe [this message]
2003-01-29 8:23 ` Benjamin Herrenschmidt
2003-01-29 8:53 ` Jens Axboe
2003-01-29 9:44 ` Benjamin Herrenschmidt
2003-01-29 10:16 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2003-01-29 8:23 Benjamin Herrenschmidt
2003-01-27 15:41 Martin MOKREJŠ
2003-01-27 16:53 ` Ross Biro
2003-01-27 17:13 ` Martin MOKREJŠ
2003-01-27 19:23 ` Jens Axboe
2003-01-27 20:27 ` Edward Tandi
2003-01-27 20:36 ` Jeff Garzik
2003-01-27 20:47 ` Edward Tandi
2003-01-27 20:57 ` Jeff Garzik
2003-01-28 9:08 ` Alan Cox
2003-01-28 10:50 ` Martin MOKREJŠ
2003-01-27 23:18 ` J.A. Magallon
2003-01-27 23:24 ` Jens Axboe
2003-01-28 0:02 ` J.A. Magallon
2003-01-27 19:03 ` Benjamin Herrenschmidt
2003-01-27 19:21 ` Benjamin Herrenschmidt
2003-01-27 19:25 ` Jens Axboe
2003-01-27 19:45 ` Alan Cox
2003-01-27 19:49 ` 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=20030128220607.GF31566@suse.de \
--to=axboe@suse.de \
--cc=Larry.Sendlosky@storigen.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