Hello Ben, <tt>> Right now, multipath users are allowed configure devices to set the wwid > based on any udev environment variable (or even use a callout, although > this is deprecated). With this patch, that breaks.</tt> Does WWID obtained by different methods change? If it changes, we would better to modify code to keep it no change. <tt>> If the udev sets > ID_SERIAL for a device, that is its wwid, right? </tt> <tt>Yes</tt> <tt>> Do you know if rbd > devices have ID_SERIAL set? </tt> <tt>WWID has different label in uevents for different devices, I only test for</tt> <tt>SCSI devices. Now we do not support rbd divice for uevents merging, these </tt> <tt>device process as old way, it has no harm in logic. If we need to merge </tt> <tt>rbd uevents for these devices, we can add code to get wwid from uevents</tt> <tt>and it can be supported easily. </tt> Regards Tang Junhui 发件人: "Benjamin Marzinski" <bmarzins@redhat.com> 收件人: tang.junhui@zte.com.cn, 抄送: christophe.varoqui@opensvc.com, hare@suse.de, mwilck@suse.com, bart.vanassche@sandisk.com, dm-devel@redhat.com, zhang.kai16@zte.com.cn, tang.wenjun3@zte.com.cn 日期: 2017/01/04 06:03 主题: Re: [PATCH 01/12] libmultipath: add wwid for "struct uevent" to record wwid of uevent <hr noshade> <tt>On Tue, Dec 27, 2016 at 04:03:18PM +0800, tang.junhui@zte.com.cn wrote: > From: tang.junhui <tang.junhui@zte.com.cn> > > Add "char *wwid" to point WWID of uevent. This member identifies > the LUN ID which the path belongs to, and it is used for merging > uevents. WWID possibly did not exist in uevent yet, so ->wwid > would be NULL, those uevents would not be merged, but be proccessed > as old way. Right now, multipath users are allowed configure devices to set the wwid based on any udev environment variable (or even use a callout, although this is deprecated). With this patch, that breaks. If the udev sets ID_SERIAL for a device, that is its wwid, right? Do you know if rbd devices have ID_SERIAL set? If so, this change will break them. Even if this change doesn't break any devices in their default configurations, we would need to disallow changing how the wwid is set for this patch to be safe. -Ben > > Change-Id: Ie6b076363b3735dc7de10184b27fa799b499af0e > Signed-off-by: tang.junhui <tang.junhui@zte.com.cn> > --- > libmultipath/uevent.c | 2 ++ > libmultipath/uevent.h | 1 + > 2 files changed, 3 insertions(+) > > diff --git a/libmultipath/uevent.c b/libmultipath/uevent.c > index 7edcce1..ef1bafe 100644 > --- a/libmultipath/uevent.c > +++ b/libmultipath/uevent.c > @@ -424,6 +424,8 @@ struct uevent *uevent_from_udev_device(struct udev_device *dev) > uev->devpath = uev->envp[i] + 8; > if (strcmp(name, "ACTION") == 0) > uev->action = uev->envp[i] + 7; > + if (strcmp(name, "ID_SERIAL") == 0) > + uev->wwid = uev->envp[i] + 10; > i++; > if (i == HOTPLUG_NUM_ENVP - 1) > break; > diff --git a/libmultipath/uevent.h b/libmultipath/uevent.h > index 9d22dcd..7bfccef 100644 > --- a/libmultipath/uevent.h > +++ b/libmultipath/uevent.h > @@ -22,6 +22,7 @@ struct uevent { > char *devpath; > char *action; > char *kernel; > + char *wwid; > unsigned long seqnum; > char *envp[HOTPLUG_NUM_ENVP]; > }; > -- > 2.8.1.windows.1 > </tt>