> -----Original Message----- > From: Christoph Hellwig [mailto:h...@infradead.org] > Sent: Tuesday, August 19, 2014 10:55 AM > To: KY Srinivasan > Cc: h...@suse.de; linux-ker...@vger.kernel.org; > de...@linuxdriverproject.org; oher...@suse.com; > jbottom...@parallels.com; linux-s...@vger.kernel.org; Martin K. Petersen > Subject: Re: [PATCH 2/2] Drivers: scsi: storvsc: Force discovery of LUNs that > may have been removed. > > On Sat, Aug 16, 2014 at 08:09:48PM -0700, K. Y. Srinivasan wrote: > > The host asks the guest to scan when a LUN is removed or added. > > The only way a guest can identify the removed LUN is when an I/O is > > attempted on a removed LUN - the SRB status code indicates that the > > LUN is invalid. We currently handle this SRB status and remove the device. > > > > Rather than waiting for an I/O to remove the device, force the > > discovery of LUNs that may have been removed prior to discovering LUNs > > that may have been added. > > This looks pretty reasonable to me, but I wonder if we should move this up > to common code so that it happens for any host rescan triggered by sysfs or > other drivers as well. Ping. Any decision on if/when this patch may be checked in.
Regards, K. Y _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
