mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "John Stoffel" <john@stoffel.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: David Miller <davem@davemloft.net>,
	fujita.tomonori@lab.ntt.co.jp, linux-kernel@vger.kernel.org
Subject: Re: IDE crash...
Date: Tue, 23 Oct 2007 11:10:24 -0400	[thread overview]
Message-ID: <18206.3808.849690.113159@stoffel.org> (raw)
In-Reply-To: <20071023074554.GA5059@kernel.dk>

>>>>> "Jens" == Jens Axboe <jens.axboe@oracle.com> writes:

Jens> On Tue, Oct 23 2007, David Miller wrote:
>> From: Jens Axboe <jens.axboe@oracle.com>
>> Date: Tue, 23 Oct 2007 09:23:59 +0200
>> 
>> > On Tue, Oct 23 2007, David Miller wrote:
>> > > From: Jens Axboe <jens.axboe@oracle.com>
>> > > Date: Tue, 23 Oct 2007 09:09:33 +0200
>> > > 
>> > > > Eh this wont work, it's the wrong entry... Here's a temporary
>> > > > work-around.
>> > > > 
>> > > > diff --git a/drivers/ide/ide-io.c b/drivers/ide/ide-io.c
>> > > > index c89f0d3..108202b 100644
>> > > > --- a/drivers/ide/ide-io.c
>> > > > +++ b/drivers/ide/ide-io.c
>> > > > @@ -822,6 +822,7 @@ void ide_map_sg(ide_drive_t *drive, struct request *rq)
>> > > >  		return;
>> > > >  
>> > > >  	if (rq->cmd_type != REQ_TYPE_ATA_TASKFILE) {
>> > > > +		sg_init_table(hwif->sg_table, hwif->sg_max_nents);
>> > > >  		hwif->sg_nents = blk_rq_map_sg(drive->queue, rq, sg);
>> > > >  	} else {
>> > > >  		sg_init_one(sg, rq->buffer, rq->nr_sectors * SECTOR_SIZE);
>> > > 
>> > > That's the exact patch I'm about to boot test :-)
>> > 
>> > That should work - once you verify that, would you mind testing this one
>> > as well? Thanks!
>> 
>> This one works here too, thanks.

Jens> Great, thanks for testing that as well. Thinking a bit more
Jens> about it, I think the forced clear should stay in
Jens> blk_rq_map_sg() since we don't want to advertise it to
Jens> drivers. So I'll just open-code it in there.

Should there be more bounds checking here, so that if you try to do a
_force() you at least check to make sure that there's something beyond
there and useable on the list?  

We're saving the time from not reallocating from scratch, but let's
make it robust by doing at least some more checks here.

John

  reply	other threads:[~2007-10-23 15:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23  6:50 David Miller
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 [this message]
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=18206.3808.849690.113159@stoffel.org \
    --to=john@stoffel.org \
    --cc=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

all inboxes | Powered by JetHome®