From: Jens Axboe <axboe@suse.de>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Using scsi_cmd->request->nr_hw_segments within a LLDD...
Date: Wed, 22 Sep 2004 17:02:55 +0200 [thread overview]
Message-ID: <20040922150255.GK2375@suse.de> (raw)
In-Reply-To: <20040922150120.GA14069@beaverton.ibm.com>
On Wed, Sep 22 2004, Patrick Mansfield wrote:
> On Wed, Sep 22, 2004 at 08:57:27AM +0200, Jens Axboe wrote:
> > On Tue, Sep 21 2004, Andrew Vasquez wrote:
>
> > Would this by any chance be from request initiated with SG_IO? This
> > problem should be fixed in 2.6.9-rcX, are you still seeing it?
> >
> > ->nr_hw_segments was not initialized for some paths earlier, so it
> > contained random crap.
>
> Jens,
>
> What code change is it? I thought it was already in 2.6.8.
Yes it was already in 2.6.8, I just wasn't sure. It's the
bio_copy_user() stuff that replaces the kmalloc() approach for unaligned
user data.
--
Jens Axboe
prev parent reply other threads:[~2004-09-22 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 21:55 Using scsi_cmd->request->nr_hw_segments within a LLDD Andrew Vasquez
2004-09-22 6:57 ` Jens Axboe
2004-09-22 15:01 ` Patrick Mansfield
2004-09-22 15:02 ` Jens Axboe [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=20040922150255.GK2375@suse.de \
--to=axboe@suse.de \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).