linux-kernel - [PATCH v2]PCI: hv: fix PCI-BUS domainID corruption

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: <3110FB76-7E16-4240-A5C0-135DD0E6EEE6@microsoft.com>
Date:   Wed, 14 Mar 2018 18:08:24 +0000
From:   Sridhar Pitchai <Sridhar.Pitchai@...rosoft.com>
To:     Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        "Michael Kelley (EOSG)" <Michael.H.Kelley@...rosoft.com>
CC:     Bjorn Helgaas <bhelgaas@...gle.com>,
        Jake Oshins <jakeo@...rosoft.com>,
        Haiyang Zhang <haiyangz@...rosoft.com>,
        Stephen Hemminger <sthemmin@...rosoft.com>,
        Dexuan Cui <decui@...rosoft.com>,
        KY Srinivasan <kys@...rosoft.com>,
        "devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
        "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: [PATCH v2]PCI: hv: fix PCI-BUS domainID corruption

    Whenever PCI bus is added, HyperV guarantees the BUS id is unique. Even with
    that when a first device is added to the bus, it overrides bus domain ID with
    the device serial number. Sometime this can result in BUS ID not being unique.
    In this case, when PCI_BUS and a device added to the bus, even before the PCI
    BUS is added to kernel, the first device tends to overwrite the domain ID with
    0. Since there exists a PCI bus with domain ID 0 already the PCI bus addition
    fails. This patch make sure when a device is added to a bus, it never updated
    the bus domain ID. Since we have the transparent SRIOV mode now, the short VF
    device name is no longer needed.
    
    Fixes: 4a9b0933bdfc("PCI:hv:Use device serial number as PCI domain")
    Cc: stable@...r.kernel.org
    Signed-off-by: Sridhar Pitchai <srpitcha@...rosoft.com>
    ---
    
    Changes in v2:
    * fix the commit comments.
    ---
     drivers/pci/host/pci-hyperv.c | 11 -----------
     1 file changed, 11 deletions(-)
    
    diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
    index 2faf38e..ac67e56 100644
    --- a/drivers/pci/host/pci-hyperv.c
    +++ b/drivers/pci/host/pci-hyperv.c
    @@ -1518,17 +1518,6 @@ static struct hv_pci_dev *new_pcichild_device(struct hv_pcibus_device *hbus,
     	get_pcichild(hpdev, hv_pcidev_ref_childlist);
     	spin_lock_irqsave(&hbus->device_list_lock, flags);
     
    -	/*
    -	 * When a device is being added to the bus, we set the PCI domain
    -	 * number to be the device serial number, which is non-zero and
    -	 * unique on the same VM.  The serial numbers start with 1, and
    -	 * increase by 1 for each device.  So device names including this
    -	 * can have shorter names than based on the bus instance UUID.
    -	 * Only the first device serial number is used for domain, so the
    -	 * domain number will not change after the first device is added.
    -	 */
    -	if (list_empty(&hbus->children))
    -		hbus->sysdata.domain = desc->ser;
     	list_add_tail(&hpdev->list_entry, &hbus->children);
     	spin_unlock_irqrestore(&hbus->device_list_lock, flags);
     	return hpdev;
    -- 
    2.7.4