From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: "Elliott, Robert (Server Storage)" <Elliott@hp.com>
Cc: Jeremy Linton <jlinton@tributary.com>,
Rob Evers <revers@redhat.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>,
"bvanassche@acm.org" <bvanassche@acm.org>,
"emilne@redhat.com" <emilne@redhat.com>
Subject: Re: [PATCH V3 1/4] Encapsulate scsi_do_report_luns
Date: Thu, 07 Mar 2013 17:30:38 +0000 [thread overview]
Message-ID: <1362677438.9043.6.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <94D0CD8314A33A4D9D801C0FE68B402950DA733C@G9W0745.americas.hpqcorp.net>
On Thu, 2013-03-07 at 17:01 +0000, Elliott, Robert (Server Storage)
wrote:
> Good point; INQUIRY, REPORT LUNS, REQUEST SENSE, and NOTIFY DATA
> TRANSFER DEVICE do not report unit attention conditions.
Well, yes they do, at least on several devices I have here.
Can I point out again that we can't code to SAM ... we have to code to
what already exists. SAM is useful as a guideline, but it isn't gospel.
In particular where the real world does something SAM says it shouldn't
(like sending UA to INQUIRY), we have to go with the real world.
This also means we can't go through the linux SCSI subsystem changing
behaviour based on what SAM says the behaviour should be. Most of what
the SCSI subsystem does is an accumulation based on years of trying to
fix it for annoying and out of spec devices.
James
next prev parent reply other threads:[~2013-03-07 17:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 13:38 [PATCH V3 0/4] Configure number of LUs reported by 'report-luns' Rob Evers
2013-03-07 13:38 ` [PATCH V3 1/4] Encapsulate scsi_do_report_luns Rob Evers
2013-03-07 15:47 ` Elliott, Robert (Server Storage)
2013-03-07 16:06 ` Jeremy Linton
2013-03-07 17:01 ` Elliott, Robert (Server Storage)
2013-03-07 17:30 ` James Bottomley [this message]
2013-03-07 17:38 ` Elliott, Robert (Server Storage)
2013-03-07 17:48 ` James Bottomley
2013-03-07 17:42 ` Jeremy Linton
2013-03-07 13:38 ` [PATCH V3 2/4] Configure reported luns Rob Evers
2013-03-07 13:38 ` [PATCH V3 3/4] Change kmallocs in report_luns to use GFP_KERNEL Rob Evers
2013-03-07 13:38 ` [PATCH V3 4/4] Use set/get_unaligned_be32 in report_luns Rob Evers
2013-03-07 14:31 ` [PATCH V3 0/4] Configure number of LUs reported by 'report-luns' Ewan Milne
2013-03-07 17:01 ` Rob Evers
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=1362677438.9043.6.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=Elliott@hp.com \
--cc=bvanassche@acm.org \
--cc=emilne@redhat.com \
--cc=jlinton@tributary.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=revers@redhat.com \
/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