From: Paolo Bonzini <pbonzini@redhat.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] sd: do not set changed flag on all unit attention conditions
Date: Mon, 16 Jul 2012 19:20:22 +0200 [thread overview]
Message-ID: <50044D56.6000400@redhat.com> (raw)
In-Reply-To: <1342455503.3176.42.camel@dabdike.int.hansenpartnership.com>
Il 16/07/2012 18:18, James Bottomley ha scritto:
>> > diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
>> > index b583277..6d8ca08 100644
>> > --- a/drivers/scsi/scsi_lib.c
>> > +++ b/drivers/scsi/scsi_lib.c
>> > @@ -843,8 +843,11 @@ void scsi_io_completion(struct scsi_cmnd *cmd, unsigned int good_bytes)
>> > } else if (sense_valid && !sense_deferred) {
>> > switch (sshdr.sense_key) {
>> > case UNIT_ATTENTION:
>> > - if (cmd->device->removable) {
>> > - /* Detected disc change. Set a bit
>> > + if (cmd->device->removable &&
>> > + (sshdr.asc == 0x3a ||
>> > + (sshdr.asc == 0x28 && sshdr.ascq == 0x00))) {
>> > + /* "No medium" or "Medium may have changed."
>> > + * This means a disc change. Set a bit
> This type of change would likely cause a huge cascade of errors in real
> removable media devices. Under the MMC standards, which a lot of the
> older removable discs seem to follow, UNIT ATTENTION indicates either
> medium change or device reset (which we check for and eat lower down);
> we can't rely on them giving proper SBC-2 sense codes. If you want to
> pretend to be removable media, you have to conform to its standards.
Would you accept a patch doing the opposite, i.e. passing some sense
codes such as PARAMETERS CHANGED and TARGET OPERATING CONDITIONS HAVE
CHANGED?
Paolo
next prev parent reply other threads:[~2012-07-16 17:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 16:06 [PATCH] sd: do not set changed flag on all unit attention conditions Paolo Bonzini
2012-07-16 16:18 ` James Bottomley
2012-07-16 17:20 ` Paolo Bonzini [this message]
2012-07-17 7:45 ` James Bottomley
2012-07-17 8:34 ` Paolo Bonzini
2012-07-17 8:40 ` James Bottomley
2012-07-17 8:54 ` Paolo Bonzini
2012-07-17 9:11 ` James Bottomley
2012-07-17 9:28 ` Paolo Bonzini
2012-07-17 12:21 ` James Bottomley
2012-07-17 12:31 ` Paolo Bonzini
2012-07-17 13:32 ` James Bottomley
2012-07-17 16:36 ` Christoph Hellwig
2012-07-17 16:47 ` Paolo Bonzini
2012-07-17 16:50 ` Christoph Hellwig
2012-07-17 18:45 ` Mike Christie
2012-07-17 18:49 ` Mike Christie
2012-07-17 21:12 ` Paolo Bonzini
2012-07-17 21:59 ` James Bottomley
2012-07-27 10:16 ` Hannes Reinecke
2012-07-25 12:09 ` Hannes Reinecke
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=50044D56.6000400@redhat.com \
--to=pbonzini@redhat.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--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