From: Douglas Gilbert <dgilbert@interlog.com>
To: linux-scsi@vger.kernel.org
Subject: sense data for status GOOD
Date: Tue, 30 Mar 2010 12:01:03 -0400 [thread overview]
Message-ID: <4BB2203F.1060409@interlog.com> (raw)
The folk at t10.org slipped this innocuous looking
addition into sam5r04 section 5.3.1 on status codes.
"Sense data may be delivered in the buffer defined by
the Sense Data argument of the Execute Command
procedure call (see 5.1) for any status code."
Previously sense data was only valid for status
CHECK_CONDITION [0x2] (and the obsolete
COMMAND_TERMINATED [0x22]). The quoted section in
the previous paragraph means that sense data could
arrive with any status code.
And now with draft sbc3r22 there is an example:
status=GOOD, sense_key=COMPLETED (recently added)
additional_sense_qualifier="INSPECT REFERRALS
SENSE DESCRIPTORS". Referrals are new and explained
in sbc3r22. IMO only a very small audience would
be interested in them. However it does indicate
a new trend.
So the question for the Linux scsi subsystem is
does it (or can it without many changes) convey
"non CHECK_CONDITION" sense data back up from
an initiator (LLD) to code that might care?
Doug Gilbert
next reply other threads:[~2010-03-30 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 16:01 Douglas Gilbert [this message]
2010-04-06 12:15 ` sense data for status GOOD Boaz Harrosh
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=4BB2203F.1060409@interlog.com \
--to=dgilbert@interlog.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;
as well as URLs for NNTP newsgroup(s).