de...@linuxdriverproject.org; linux-ker...@vger.kernel.org; Haiyang
> Zhang
> >>
> >> Subject: Re: [PATCH 0/2] Drivers: hv: vmbus: make bus ids in sysfs
> >> persistent
> >>
> >> KY Srinivasan writes:
> >>
> >> >> -Original Message-
6 1:46 AM
>> >> To: de...@linuxdriverproject.org
>> >> Cc: linux-ker...@vger.kernel.org; Haiyang Zhang
>> >> ; KY Srinivasan
>> >> Subject: [PATCH 0/2] Drivers: hv: vmbus: make bus ids in sysfs
>> >> persistent
>> >>
>> &
t;> Cc: linux-ker...@vger.kernel.org; Haiyang Zhang
> >> ; KY Srinivasan
> >> Subject: [PATCH 0/2] Drivers: hv: vmbus: make bus ids in sysfs
> >> persistent
> >>
> >> Bus ids for VMBus devices in /sys/bus/vmbus/devices/ are not
> >> guaranteed to be pe
>> Subject: [PATCH 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent
>>
>> Bus ids for VMBus devices in /sys/bus/vmbus/devices/ are not guaranteed
>> to be persistent across reboot or kernel restart and this causes problems
>> for some tools. E.g. kexec tools use t
> -Original Message-
> From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com]
> Sent: Tuesday, August 9, 2016 1:46 AM
> To: de...@linuxdriverproject.org
> Cc: linux-ker...@vger.kernel.org; Haiyang Zhang ;
> KY Srinivasan
> Subject: [PATCH 0/2] Drivers: hv: vmbus:
Bus ids for VMBus devices in /sys/bus/vmbus/devices/ are not guaranteed
to be persistent across reboot or kernel restart and this causes problems
for some tools. E.g. kexec tools use these ids to identify NIC on kdump.
Fix the issue by using relid from channel offer as the unique id instead
of an a
