From: Hannes Reinecke <hare@suse.de>
To: James Smart <james.smart@avagotech.com>,
Johannes Thumshirn <jthumshirn@suse.de>,
"James E.J. Bottomley" <JBottomley@odin.com>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] scsi: Export SCSI Inquiry data to sysfs
Date: Fri, 14 Aug 2015 14:53:30 +0200 [thread overview]
Message-ID: <55CDE4CA.6060703@suse.de> (raw)
In-Reply-To: <55CDDEBB.1040402@avagotech.com>
On 08/14/2015 02:27 PM, James Smart wrote:
> On 8/14/2015 2:32 AM, Hannes Reinecke wrote:
>> On 08/13/2015 01:50 PM, Johannes Thumshirn wrote:
>>> Export the RAW SCSI Inquiry to sysfs as binfile. This way the
>>> data can be used by userlang without the need to have and ioctl or use the
>>> sg_inq tool.
>>>
>> userland!
>>
>
> Just be careful. There are conditions where this could be stale
> data.... LUN reconfig on an array that hasn't been rescanned by
> the mid layer yet is such a case.
>
> Any reason you didn't have the sysfs call initiate a lun scan or
> send an inquiry so it's always valid data ?
>
Currently the SCSI stack doesn't do LUN rescanning; the only way
to recover from stale data is to remove the device and initiate
a host rescan. That's why we have tools like rescan-scsi-bus.sh etc.
We're working on moving the SCSI stack to do a LUN rescanning, but
that's still future stuff.
So this patch just displays the status quo, without any added
functionality.
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)
prev parent reply other threads:[~2015-08-14 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 11:50 [PATCH] scsi: Export SCSI Inquiry data to sysfs Johannes Thumshirn
2015-08-14 6:32 ` Hannes Reinecke
2015-08-14 12:27 ` James Smart
2015-08-14 12:53 ` 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=55CDE4CA.6060703@suse.de \
--to=hare@suse.de \
--cc=JBottomley@odin.com \
--cc=james.smart@avagotech.com \
--cc=jthumshirn@suse.de \
--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 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.