From: Hannes Reinecke <hare@suse.de>
To: Bart Van Assche <bvanassche@acm.org>,
James Bottomley <jbottomley@parallels.com>
Cc: linux-scsi@vger.kernel.org, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCHv7 0/3][Resend] Display EVPD pages in sysfs
Date: Wed, 05 Mar 2014 09:34:47 +0100 [thread overview]
Message-ID: <5316E1A7.8000308@suse.de> (raw)
In-Reply-To: <5316DF09.4070704@acm.org>
On 03/05/2014 09:23 AM, Bart Van Assche wrote:
> On 03/05/14 09:00, Hannes Reinecke wrote:
>> On 03/02/2014 09:53 AM, Bart Van Assche wrote:
>>> A general comment about this patch series: I think the cached copies of
>>> these pages should be refreshed at least after an INQUIRY DATA HAS
>>> CHANGED unit attention code has been received. Some SCSI target
>>> implementations allow to change this data after a LUN has been created.
>>
>> Yes, eventually. But this needs to be handled in a general context,
>> as (potentially) even the inquiry string itself has been invalidated
>> after receiving such an event.
>> So we should be doing a rescan of the scsi device upon receiving
>> such an event. But this is a general problem, not one particular to
>> this patchset.
>
> Sorry but since the ALUA patch series is based on this patch series I'm
> afraid that the ALUA patch series introduces a regression that seems
> unacceptable to me. SCSI target implementations like LIO allow to remove
> and re-add a LUN after initial discovery of a SCSI host. My concern here
> is that the caching introduced by this patch series and which is used in
> the ALUA patch series will cause INQUIRY data not to be updated after it
> has been changed at the target side. Today the scsi_dh_alua handler
> processes such INQUIRY data changes fine. Does this make sense to you ?
>
Currently, the SCSI stack itself is not well-equipped to handle
these kind of setups anyway.
(The only known working solution is to remove the device _entirely_
and have the HBA rescan the LUN).
So while you are right I'm still preferring to keep those two issues
separate.
James, any preferences here?
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
prev parent reply other threads:[~2014-03-05 8:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 10:27 [PATCHv7 0/3][Resend] Display EVPD pages in sysfs Hannes Reinecke
2014-02-13 10:27 ` [PATCH 1/3] scsi_sysfs: Implement 'is_visible' callback Hannes Reinecke
2014-02-13 10:28 ` [PATCH 2/3] Add EVPD page 0x83 to sysfs Hannes Reinecke
2014-03-02 8:34 ` Bart Van Assche
2014-03-05 7:56 ` Hannes Reinecke
2014-03-02 8:36 ` Bart Van Assche
2014-03-05 7:56 ` Hannes Reinecke
2014-02-13 10:28 ` [PATCH 3/3] Add EVPD page 0x80 " Hannes Reinecke
2014-02-28 7:27 ` [PATCHv7 0/3][Resend] Display EVPD pages in sysfs Hannes Reinecke
2014-03-02 8:53 ` Bart Van Assche
2014-03-05 8:00 ` Hannes Reinecke
2014-03-05 8:23 ` Bart Van Assche
2014-03-05 8:34 ` Hannes Reinecke [this message]
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=5316E1A7.8000308@suse.de \
--to=hare@suse.de \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--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 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.