From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [patch]liberal acceptance of 0x28 asc in sd.c
Date: Thu, 30 Oct 2008 09:01:13 -0500 [thread overview]
Message-ID: <1225375273.3250.9.camel@localhost.localdomain> (raw)
In-Reply-To: <200810301309.41705.oliver@neukum.org>
On Thu, 2008-10-30 at 13:09 +0100, Oliver Neukum wrote:
> >From reading the SCSI spec it seems that having the valid bit 0 (0x70
> checked in scsi_sense_valid) should does not invalidate the ASC or ASQ.
> [See page 37 of spc4r02.pdf].
That's a correct reading of the spec as regards the valid bit for non
descriptor sense data, but not applicable to this situation. sense_valid
is generated from (byte[0] & 0x70 == 0x70) (see scsi_sense_valid() in
include/scsi/scsi_eh.h) not from the valid bit. This test is *required*
by the standard otherwise what we have isn't sense data.
> It should only invalidate the INFORMATION
> field. Therefore remove the sense_valid check from the USB quirk.
>
> This is needed for a strange USB storage device.
Could you elaborate a bit more? What's its problem (and what is it
replying as byte 0 to a REQUEST_SENSE)?
Also:
> Signed-off-by: Brandon Philips <bphilips@suse.de>
> Signed-off-by: Oliver Neukum <oneukum@suse.de>
These signoffs don't make sense for what you sent ... this implies that
its Brandon's patch which you altered, in which case it needs a From: at
the beginning to make him the author.
James
next prev parent reply other threads:[~2008-10-30 14:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 12:09 [patch]liberal acceptance of 0x28 asc in sd.c Oliver Neukum
2008-10-30 14:01 ` James Bottomley [this message]
2008-10-30 14:23 ` Oliver Neukum
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=1225375273.3250.9.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=oliver@neukum.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