linux-kernel - Re: [PATCH 2/2] Drivers: scsi: storvsc: Force discovery of LUNs that may have been removed.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 29 Aug 2014 10:13:44 +0200
From:	Hannes Reinecke <hare@...e.de>
To:	Bart Van Assche <bvanassche@....org>,
	Mike Christie <michaelc@...wisc.edu>,
	Christoph Hellwig <hch@...radead.org>,
	"K. Y. Srinivasan" <kys@...rosoft.com>
CC:	linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
	ohering@...e.com, jbottomley@...allels.com,
	linux-scsi@...r.kernel.org,
	"Martin K. Petersen" <martin.petersen@...cle.com>
Subject: Re: [PATCH 2/2] Drivers: scsi: storvsc: Force discovery of LUNs that
 may have been removed.

On 08/29/2014 09:39 AM, Bart Van Assche wrote:
> On 08/29/14 08:19, Hannes Reinecke wrote:
>> On 08/29/2014 04:42 AM, Mike Christie wrote:
>>> How are distros handling 0x6/0x3f/0x0e (report luns changed) when it
>>> gets passed to userspace? Is everyone kicking off a new full (add and
>>> delete) scan to handle this or logging it? Is the driver returning this
>>> when the LUNs change?
>>>
>> Currently it's logged to userspace and ignored.
>> Doing an automated rescan has proven to be dangerous, as it
>> might disconnect any LUNs which are still in use by applications.
>> Especially HA or database setups tends to become very annoyed
>> when you do an automated rescan.
>
> Has it already been considered to add newly discovered LUNs
> automatically and to leave it to the user to remove stale LUNs manually
> ? That would be similar to what the rescan-scsi-bus.sh script does
> without option -r/--remove.
>

As of now we're still missing an in-kernel infrastructure which 
would allow us to react on any sense codes; currently we're relying 
on the administrator to setup a udev rule here.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@...e.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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/