From: Jens Axboe <axboe@suse.de>
To: Stuart_Hayes@Dell.com
Cc: linux-scsi@vger.kernel.org, Joshua_Giles@Dell.com
Subject: Re: [PATCH 2.6.11] ide-scsi: map sg buffers in idescsi_input/output_buffers() to kernel virtual address
Date: Wed, 16 Mar 2005 17:06:46 +0100 [thread overview]
Message-ID: <20050316160645.GW7842@suse.de> (raw)
In-Reply-To: <7A8F92187EF7A249BF847F1BF4903C04010EEA11@ausx2kmpc103.aus.amer.dell.com>
On Wed, Mar 16 2005, Stuart_Hayes@Dell.com wrote:
> Hayes, Stuart wrote:
> > This patch will map the sg buffers to kernel virtual memory space in
> > the functions idescsi_input_buffers() and idescsi_output_buffers().
> > Without this patch, idescsi passes a null pointer to
> > atapi_input_bytes() and atapi_output_bytes() when sg pages are in
> > high memory (i686 architecture).
> >
> > I'm attaching as a file, too, as the text will certainly be wrapped.
> >
> > (Sorry for the subject rename--I'm trying to use the correct format
> > for patch emails.)
> >
> > Thanks
> > Stuart
>
> And, while there's another high memory/kmap patch question on this
> list...
>
> Is there some reason nobody seems interested in this patch (except
> Jens--thanks for the help!)? I'm kind of new to sending in patches,
> and I'm not sure if I'm just not waiting long enough, or if there is
> a problem with this patch...
>
> But really, we're getting a null pointer dereference oops when using
> ATAPI tape drives (with ide-scsi) without this patch...
Sorry, that did seem to get dropped on the floor. Actually I'm wondering
why you are seeing highmem pages there in the first place, it would be
easier/better just to limit ide-scsi to non-highmem pages. That would
remove the need to add any work arounds in the driver.
--
Jens Axboe
next prev parent reply other threads:[~2005-03-16 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 15:51 [PATCH 2.6.11] ide-scsi: map sg buffers in idescsi_input/output_buffers() to kernel virtual address Stuart_Hayes
2005-03-16 16:06 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-31 21:38 Stuart_Hayes
2005-03-23 23:46 Stuart_Hayes
2005-03-17 21:45 Stuart_Hayes
2005-03-18 8:14 ` Jens Axboe
2005-03-17 20:14 Stuart_Hayes
2005-03-17 20:33 ` Jens Axboe
2005-03-17 21:33 ` Jens Axboe
2005-03-16 20:30 Stuart_Hayes
2005-03-17 16:21 ` Jens Axboe
2005-03-09 20:26 Stuart_Hayes
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=20050316160645.GW7842@suse.de \
--to=axboe@suse.de \
--cc=Joshua_Giles@Dell.com \
--cc=Stuart_Hayes@Dell.com \
--cc=linux-scsi@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