From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752400AbcHIIqZ (ORCPT ); Tue, 9 Aug 2016 04:46:25 -0400 Received: from mx1.redhat.com ([209.132.183.28]:51034 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751454AbcHIIqW (ORCPT ); Tue, 9 Aug 2016 04:46:22 -0400 From: Vitaly Kuznetsov To: devel@linuxdriverproject.org Cc: linux-kernel@vger.kernel.org, Haiyang Zhang , "K. Y. Srinivasan" Subject: [PATCH 0/2] Drivers: hv: vmbus: make bus ids in sysfs persistent Date: Tue, 9 Aug 2016 10:46:17 +0200 Message-Id: <1470732379-5013-1-git-send-email-vkuznets@redhat.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.31]); Tue, 09 Aug 2016 08:46:22 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 auto incremented counter. Vitaly Kuznetsov (2): Drivers: hv: make VMBus bus ids persistent Drivers: hv: get rid of id in struct vmbus_channel drivers/hv/channel_mgmt.c | 2 -- drivers/hv/vmbus_drv.c | 2 +- include/linux/hyperv.h | 3 --- 3 files changed, 1 insertion(+), 6 deletions(-) -- 2.7.4