Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Paul Bolle <pebolle@tiscali.nl>,
	"James E.J. Bottomley" <JBottomley@parallels.com>,
	Matthew Dharm <mdharm-usb@one-eyed-alien.net>,
	linux-scsi@vger.kernel.org, usb-storage@lists.one-eyed-alien.net,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] scsi: usb-storage: hide errors for five devices
Date: Tue, 15 May 2012 08:35:39 -0700	[thread overview]
Message-ID: <20120515153539.GA25206@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1205081240450.1479-100000@iolanthe.rowland.org>

On Tue, May 08, 2012 at 01:03:17PM -0400, Alan Stern wrote:
> On Tue, 8 May 2012, Paul Bolle wrote:
> 
> > On Tue, 2012-05-08 at 10:02 -0400, Alan Stern wrote:
> > > On Tue, 8 May 2012, Paul Bolle wrote: 
> > > > 1) These patches try to hide those errors by:
> > > > - downgrading one error to a notice; and
> > > 
> > > That's a reasonable thing to do, IMO.
> > > 
> > > > - setting the NO_WP_DETECT quirk for these five devices.
> > > 
> > > But that isn't.  These quirks are intended for devices that crash when
> > > they receive the command in question.
> > 
> > Yes, these USB memory sticks don't crash. (They actually seem to work
> > just fine, something that I perhaps should have emphasized in the commit
> > descriptions.)
> > 
> > > They aren't meant to suppress sending commands to devices that can
> > > properly reject them.
> > 
> > Even the sticks that hit "bad_sense" (in sd_read_cache_type(), which I
> > forgot to mention in the comment descriptions)? Is that not as severe as
> > it suggests?
> 
> It means that the device either doesn't support the MODE SENSE command
> or it returned useless data.  As a result, we will assume it has a
> write-through cache when it might not.
> 
> For memory sticks this doesn't matter.  For other devices it might be 
> more important (although anything with a working cache should not hit 
> this error case).
> 
> > Of course, an easy way out would be to downgrade both the "Asking for
> > cache data failed" and the "No Caching mode page present" errors to
> > notices. But the SCSI people might disagree with that approach.
> 
> Well, let's see what they say.

What ever happened here, are these 3 patches acceptable, or do they need
to be reworked or something else?

thanks,

greg k-h

  reply	other threads:[~2012-05-15 15:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08 10:19 [PATCH 0/3] scsi: usb-storage: hide errors for five devices Paul Bolle
2012-05-08 14:02 ` Alan Stern
2012-05-08 15:37   ` Paul Bolle
2012-05-08 17:03     ` Alan Stern
2012-05-15 15:35       ` Greg Kroah-Hartman [this message]
2012-05-15 16:29         ` Paul Bolle
2012-05-15 16:36           ` Alan Cox
2012-05-22  8:48             ` Paul Bolle
2012-05-22  9:25               ` Alan Cox

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=20120515153539.GA25206@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=JBottomley@parallels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mdharm-usb@one-eyed-alien.net \
    --cc=pebolle@tiscali.nl \
    --cc=stern@rowland.harvard.edu \
    --cc=usb-storage@lists.one-eyed-alien.net \
    /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