public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>, SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Trivial patch for scsi logging text string
Date: 15 Apr 2003 16:42:07 -0500	[thread overview]
Message-ID: <1050442929.2571.31.camel@mulgrave> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0304151524010.699-100000@ida.rowland.org>

On Tue, 2003-04-15 at 14:31, Alan Stern wrote:
> On 15 Apr 2003, James Bottomley wrote:
> 
> > On Tue, 2003-04-15 at 12:03, Greg KH wrote:
> > > Hm, I don't think I can submit scsi patches to Linus :)
> > > Why not send them to the scsi maintainers...
> > 
> > The SCSI maintainers are linux-scsi@vger.kernel.org, so we've already
> > been copied on this one.
> > 
> > James
> 
> Does that mean that linux-scsi will forward my patch to Linus?  I hope so,
> because I've got another one to submit (to Marcelo), more substantive this
> time.

Yes, for 2.5

> In 2.4.21-pre7, when the scsi error-handler decides that it has cleaned 
> things up and retries the original command, it neglects to zero out the 
> command's sense buffer first.  In all likelihood the sense buffer will 
> contain old data left over from the error recovery operations.  This 
> confuses scan_scsis(), which thinks that because there is valid sense data 
> its INQUIRY probe must have failed.  This patch clears the sense buffer 
> before a retry.
> 
> If nobody on the linux-scsi list objects to it, this patch should be 
> applied.

2.4 is more tricky.  Since fixing 2.5 is pretty much a full time job,
there's no-one really who looks after SCSI in 2.4.  It's probably best
to send it to Marcelo along with an explanation of what the problem is.

James



  reply	other threads:[~2003-04-15 21:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15  6:33 [PATCH] 2.5.67+ scsi_release_request call queue next Mike Anderson
2003-04-15 15:01 ` Trivial patch for scsi logging text string Alan Stern
2003-04-15 17:03   ` Greg KH
2003-04-15 17:10     ` James Bottomley
2003-04-15 19:31       ` Alan Stern
2003-04-15 21:42         ` James Bottomley [this message]
2003-04-15 19:39 ` [PATCH] 2.5.67+ scsi_release_request call queue next Alan Stern
2003-04-15 22:36   ` Mike Anderson

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=1050442929.2571.31.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=greg@kroah.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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