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: Tue, 17 Jul 2012 14:31:21 +0200 [thread overview]
Message-ID: <50055B19.8090101@redhat.com> (raw)
In-Reply-To: <1342527693.3039.64.camel@dabdike.int.hansenpartnership.com>
Il 17/07/2012 14:21, James Bottomley ha scritto:
>> Yes, I realize failing only on specific sense codes as I did it in the
>> patch is not going to work. However, the other way round is not
>> problematic (explicitly allow some sense codes, fail on all others).
>
> Heh, I once thought that, but there's no end to the strange ideas USB
> manufacturers get.
:)
>> > Another example is "target operating conditions have changed". QEMU
>> > cannot report such changes because scsi_error prints a warning (fine)
>> > and then passes the unit attention upwards. With removable drives, this
>> > has the same problem as resizing.
> Why would a removable device ever use any of the codes under this ASC
> when the medium hasn't changed? They're all for arrays (well except
> 0x10 and 0x11 ... and they're only supposed to apply to tape changers
> with autoload support declared in the control mode page).
There are also a couple of generic ones such as "reported luns have
changed". I also considered briefly using "inquiry data has changed" to
reload the unmap parameters after live snapshot or storage migration. I
dropped the idea, please don't put me in the same bin as the USB
manufacturers.
Paolo
next prev parent reply other threads:[~2012-07-17 12:31 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
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 [this message]
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=50055B19.8090101@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