Re: [PATCH] scsi-misc-2.5 remove scsi_scan.c EVPD code

[James Bottomley <James.Bottomley@steeleye.com>]

On Mon, 2003-05-05 at 10:52, Mike Anderson wrote:
> James Bottomley [James.Bottomley@steeleye.com] wrote:
> Mutability should not depend on how a uuid is set. It should depend on
> what can change it.

I think the sysfs write API is sufficient, so it has to be a rw-r-r file
to allow root to write it on hotplug.

> Why block?

It's the largest available useful subset other than device itself.

> They are not unique to the block layer either. uuid's are unique to the
> name space they are acquired in. Non-block storage devices can have
> uuids. They can also have uuids without block based upper level drivers
> loaded.

True.

> If you obtain a scsi_device uuid it should not be written in to a block
> device attribute it should be attached to the struct device representing
> the scsi device. If the attribute name is consistent "uuid" than cat
> ".../device/uuid" will function the same.

by that argument, capacity, which is a property of the SCSI sd device
should be stored in the SCSI device.  It isn't, since it's a global
block device property, it's stored in the gendisk.

Unique identifiers are a property of SCSI devices, but they're not an
exclusive property.

James