public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Mansfield <patmans@us.ibm.com>
To: Doug Ledford <dledford@redhat.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-scsi mailing list <linux-scsi@vger.kernel.org>
Subject: Re: [Patch] QLogic qla2x00 driver fixes
Date: Fri, 25 Feb 2005 09:02:02 -0800	[thread overview]
Message-ID: <20050225170202.GB8539@us.ibm.com> (raw)
In-Reply-To: <1109332659.27139.224.camel@compaq-rhel4.xsintricity.com>

On Fri, Feb 25, 2005 at 06:57:39AM -0500, Doug Ledford wrote:
> On Fri, 2005-02-25 at 03:38 -0500, Jeff Garzik wrote:
> > Arjan van de Ven wrote:
> > > On Thu, 2005-02-24 at 23:21 -0500, Doug Ledford wrote:
> > > 
> > >>Don't use cmd->request->nr_hw_segments as it may not be initialized
> > >>(SG_IO in particular bypasses anything that initializes this and just
> > >>uses scsi_do_req to insert a scsi_request directly on the head of the
> > >>queue) 
> > > 
> > > 
> > > should we fix that in the SG_IO layer ?
> > 
> > Possibly/probably.

Doug,

What kernel did you hit this with? 

And same question as Doug G: is it via sg (not the block SG_IO)? sg uses
scsi_do_req(), block SG_IO doesn't.

Jens sent changes last August or so that fixed SG_IO (not sg) to always
set nr_hw_segments, change should be in 2.6.10. It is not obvious that his
change fixed this, I can't find the changeset or log.

> I'm not concerned with it personally.  The only reason that the scsi
> layer copies the block layer request struct into the scsi
> command/request is so that upon completion it has enough information to
> mark blocks as either up to date or not while at the same time allowing
> the scsi layer to free the original block request at queue time, not at
> completion time.  It was never intended to be used by low level drivers.

In 2.6, we no don't copy the request into the command:

struct scsi_cmnd {
	...
	struct request *request
	...
}

-- Patrick Mansfield

  reply	other threads:[~2005-02-25 17:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25  4:21 [Patch] QLogic qla2x00 driver fixes Doug Ledford
2005-02-25  4:28 ` Jeff Garzik
2005-02-25  6:46 ` Andrew Vasquez
2005-02-25  7:43 ` Douglas Gilbert
2005-02-25  7:57 ` Arjan van de Ven
2005-02-25  8:38   ` Jeff Garzik
2005-02-25 11:57     ` Doug Ledford
2005-02-25 17:02       ` Patrick Mansfield [this message]
2005-03-01  6:52         ` Doug Ledford
2005-02-25 17:09       ` Luben Tuikov

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=20050225170202.GB8539@us.ibm.com \
    --to=patmans@us.ibm.com \
    --cc=arjan@infradead.org \
    --cc=dledford@redhat.com \
    --cc=jgarzik@pobox.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