From: Hannes Reinecke <hare@suse.de>
To: Bart Van Assche <bvanassche@acm.org>,
emilne@redhat.com, "Elliott,
Robert (Server Storage)" <Elliott@hp.com>
Cc: "James Bottomley (jbottomley@parallels.com)"
<jbottomley@parallels.com>, Christoph Hellwig <hch@infradead.org>,
"scameron@beardog.cce.hp.com" <scameron@beardog.cce.hp.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: scsi error handling thread and REQUEST SENSE
Date: Mon, 19 May 2014 12:37:40 +0200 [thread overview]
Message-ID: <5379DEF4.9000301@suse.de> (raw)
In-Reply-To: <5379DD04.9020303@acm.org>
On 05/19/2014 12:29 PM, Bart Van Assche wrote:
> On 05/19/14 10:32, Hannes Reinecke wrote:
>> Well, problem here is that the 'REQUEST SENSE' command has two problems:
>> a) Most modern HBA (ie all non-SPI HBAs) use autosense, ie the sense
>> code is returned with the command. So issuing 'REQUEST SENSE' here is
>> pointless.
>> b) The sense code (when retrieved via 'REQUEST SENSE') relates to the
>> most recently processed command (from the target perspective).
>> Which is a bit hard to make out, as by the time SCSI EH starts
>> several other commands might have been processed already, so any
>> sense we'd be retrieving most likely does not relate to the failed command.
>>
>> I would propose to disable the 'REQUEST_SENSE' step as soon as the HBA
>> is capable of autosensing. We requires us to add another flag
>> to the scsi_host field.
>>
>> What about the attached patch? That should roughly do what's required
>> here, right?
>
> This patch does not address the SRP initiator. There might be more SCSI
> initiator drivers that support autosense but that are not addressed by
> this patch. Has it been considered to set the autosense flag for all
> HBA's and clear it in those SCSI initiator drivers that do not support
> autosense ?
>
Correct.
I haven't looked at the SRP spec to figure out if it does autosense
or not. If it does we should be updating the patch.
And yes, it has been considered.
However, I decided against it because it would require to check
each and every driver to figure out if they do autosense or not.
So as a first test I decided it to be quicker to have a 'whitelist'
kind of approach and enable only those for which autosense is
required by protocol.
This also excludes all RAID HBAs, which need to be checked
individually. And the SPI HBAs, of course.
Plus this is just a test patch, nothing official yet.
I'm happy to include the changes for SRP if you can confirm that SRP
requires autosense.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-05-19 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 19:02 scsi error handling thread and REQUEST SENSE Elliott, Robert (Server Storage)
2014-05-16 20:05 ` Ewan Milne
2014-05-19 8:32 ` Hannes Reinecke
2014-05-19 10:29 ` Bart Van Assche
2014-05-19 10:37 ` Hannes Reinecke [this message]
2014-05-19 11:26 ` Bart Van Assche
2014-05-19 13:41 ` James Bottomley
2014-05-19 15:15 ` Elliott, Robert (Server Storage)
2014-05-19 11:40 ` Bart Van Assche
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=5379DEF4.9000301@suse.de \
--to=hare@suse.de \
--cc=Elliott@hp.com \
--cc=bvanassche@acm.org \
--cc=emilne@redhat.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=scameron@beardog.cce.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.