On Fri, Jan 31 2020 at 7:55pm -0500, John Dorminy <jdorminy@xxxxxxxxxx> wrote: > While dm_device_name() returns the MAJOR:MINOR numbers of a device, > some targets would like to know the pretty name of a device, and > some targets would like to know the uuid expected for the device. > > The MAJOR:MINOR name is useful for logging, but printing the long > name of the device can make it easier for the user to correlate > messages with the device names they know in userspace. > > The UUID can be useful for devices which store a UUID on disk, and > would like to verify the on-disk UUID matches the UUID known by DM. > > dm_copy_name_and_uuid() appears to be the only way to get at the > pretty name and the UUID at present, and this change exports the > function for use by GPLd modules. > > Signed-off-by: John Dorminy <jdorminy@xxxxxxxxxx> > --- > drivers/md/dm-ioctl.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/md/dm-ioctl.c b/drivers/md/dm-ioctl.c > index 1e03bc89e20f..711a46015696 100644 > --- a/drivers/md/dm-ioctl.c > +++ b/drivers/md/dm-ioctl.c > @@ -2018,7 +2018,7 @@ int dm_copy_name_and_uuid(struct mapped_device *md, char *name, char *uuid) > > return r; > } > - > +EXPORT_SYMBOL_GPL(dm_copy_name_and_uuid); > > /** > * dm_early_create - create a mapped device in early boot. > -- > 2.20.1 These are already available to userspace via sysfs, e.g.: # dmsetup ls test-test (253:0) # cat /sys/block/dm-0/dm/name test-test # cat /sys/block/dm-0/dm/uuid LVM-IFFqf0id2DX3IgGmu6izzJW1rBoWmsC61hwGobtrD60aCMh6zJwK3uiYUS6rbNoY Verification of the UUID that a target happens to store in its ondisk metadata seems like it'd best be done by userspace, _before_ activating the DM device, no? Or are you saying that the target would do this verification as part of its .ctr method? Anyway, I'm fine with exporting it.. just think the proposed usecases are not a "slam-dunk" for why you need it. -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
