linux-kernel - Re: [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent

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]

Message-ID: <87r38kxf59.fsf@vitty.brq.redhat.com>
Date:   Fri, 16 Sep 2016 13:22:58 +0200
From:   Vitaly Kuznetsov <vkuznets@...hat.com>
To:     "K. Y. Srinivasan" <kys@...rosoft.com>
Cc:     linux-kernel@...r.kernel.org, devel@...uxdriverproject.org,
        Haiyang Zhang <haiyangz@...rosoft.com>
Subject: Re: [PATCH v2 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent

Vitaly Kuznetsov <vkuznets@...hat.com> writes:

> 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 if_instance from channel offer as the unique id
> instead of an auto incremented counter.
>
> Changes since v1:
> - Use if_instance instead of relid [K. Y. Srinivasan]
>
> Vitaly Kuznetsov (2):
>   Drivers: hv: make VMBus bus ids persistent
>   Drivers: hv: get rid of id in struct vmbus_channel
>

K. Y.,

I don't see these patches in your submissions to Greg. Could you please
pick them up (in case there are no issues with them in your opinion, of
course).

Thanks!

>  drivers/hv/channel_mgmt.c | 2 --
>  drivers/hv/vmbus_drv.c    | 4 ++--
>  include/linux/hyperv.h    | 3 ---
>  3 files changed, 2 insertions(+), 7 deletions(-)

-- 
  Vitaly