From: Hannes Reinecke <hare@suse.de>
To: emilne@redhat.com
Cc: James Bottomley <james.bottomley@hansenpartnership.com>,
linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Nic Bellinger <nab@daterainc.com>
Subject: Re: [PATCH] scsi: retry MODE SENSE on unit attention
Date: Fri, 12 Jun 2015 08:27:31 +0200 [thread overview]
Message-ID: <557A7BD3.7040607@suse.de> (raw)
In-Reply-To: <1434035231.27387.111.camel@localhost.localdomain>
On 06/11/2015 05:07 PM, Ewan Milne wrote:
> On Thu, 2015-06-11 at 13:01 +0200, Hannes Reinecke wrote:
>> The 'sd' driver is calling scsi_mode_sense() to figure out
>> internal details. But scsi_mode_sense() never checks for
>> any pending unit attentions, so we're getting annoying error
>> messages like:
>>
>> MODE SENSE: unimplemented page/subpage: 0x00/0x00
>>
>> and a possible wrong decision for device cache handling.
>>
>> Signed-off-by: Hannes Reinecke <hare@suse.de>
>> ---
>> drivers/scsi/scsi_lib.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
>> index 2428d96..d7915c8 100644
>> --- a/drivers/scsi/scsi_lib.c
>> +++ b/drivers/scsi/scsi_lib.c
>> @@ -2423,7 +2423,7 @@ scsi_mode_sense(struct scsi_device *sdev, int dbd, int modepage,
>> unsigned char cmd[12];
>> int use_10_for_ms;
>> int header_length;
>> - int result;
>> + int result, retry_count = retries;
>> struct scsi_sense_hdr my_sshdr;
>>
>> memset(data, 0, sizeof(*data));
>> @@ -2502,6 +2502,11 @@ scsi_mode_sense(struct scsi_device *sdev, int dbd, int modepage,
>> data->block_descriptor_length = buffer[3];
>> }
>> data->header_length = header_length;
>> + } else if ((status_byte(result) == CHECK_CONDITION) &&
>> + scsi_sense_valid(sshdr) &&
>> + sshdr->sense_key == UNIT_ATTENTION && retry_count) {
>> + retry_count--;
>> + goto retry;
>> }
>>
>> return result;
>
> Great, but shouldn't we be doing this more generally? What about
> scsi_mode_select()?
>
I haven't seen any issues with scsi_mode_select() as of now, so I
didn't do anything about this :-)
> (And, with the number of status changes that can get reported by
> UAs, we might want to think about increasing the retry count on
> these commands up from 3 at some point.)
>
Hmm. _Actually_, we're not getting _more_ UAs (neither the number
nor the situation at which UAs are being send has changed).
It's just that we're trying to _use_ UAs so these things pop up.
But yeah, raising the number or retries to eg 5 is probably a good idea.
> Reviewed-by: Ewan D. Milne <emilne@redhat.com>
>
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (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:[~2015-06-12 6:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 11:01 [PATCH] scsi: retry MODE SENSE on unit attention Hannes Reinecke
2015-06-11 15:07 ` Ewan Milne
2015-06-12 6:27 ` Hannes Reinecke [this message]
2015-06-12 14:08 ` Ewan Milne
-- strict thread matches above, loose matches on Subject: below --
2015-06-12 14:12 Hannes Reinecke
2015-07-06 11:16 Hannes Reinecke
2015-07-06 15:19 ` 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=557A7BD3.7040607@suse.de \
--to=hare@suse.de \
--cc=emilne@redhat.com \
--cc=hch@lst.de \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@daterainc.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;
as well as URLs for NNTP newsgroup(s).