On Sat, 2014-03-15 at 09:51 +0100, Hannes Reinecke wrote:
Add a flag 'vpd_invalid' to the SCSI device to indicate that
the VPD data needs to be refreshed. This is required if either
a manual rescan is triggered or if the sense code INQUIRY DATA
HAS CHANGED has been received.
Signed-off-by:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/17/2014 11:11 PM, Jeremy Linton wrote:
On 3/15/2014 3:51 AM, Hannes Reinecke wrote:
Add a flag 'vpd_invalid' to the SCSI device to indicate that
the VPD data needs to be refreshed. This is required if
either a manual rescan is triggered or
On Tue, 2014-03-18 at 07:52 +0100, Hannes Reinecke wrote:
On 03/17/2014 11:11 PM, Jeremy Linton wrote:
On 3/15/2014 3:51 AM, Hannes Reinecke wrote:
Add a flag 'vpd_invalid' to the SCSI device to indicate that
the VPD data needs to be refreshed. This is required if
either a manual rescan
On 03/17/2014 11:11 PM, Jeremy Linton wrote:
I didn't study the whole code path but does the VPD data get
updated on a 6/2900? I suspect it should be. I can imagine a
number of cases where the luns changed check condition gets
preempted/lost by a device reset. I guess much of that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 3/15/2014 3:51 AM, Hannes Reinecke wrote:
Add a flag 'vpd_invalid' to the SCSI device to indicate that the VPD data
needs to be refreshed. This is required if either a manual rescan is
triggered or if the sense code INQUIRY DATA HAS CHANGED has
Add a flag 'vpd_invalid' to the SCSI device to indicate that
the VPD data needs to be refreshed. This is required if either
a manual rescan is triggered or if the sense code INQUIRY DATA
HAS CHANGED has been received.
Signed-off-by: Hannes Reinecke h...@suse.de
---
drivers/scsi/scsi.c|
6 matches
Mail list logo
