linux-kernel - Re: [PATCH 1/2] PCI: save and restore device state during bus reset

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: <46a47bf2-ab39-0ee2-0faf-2f4050f2a89d@codeaurora.org>
Date:   Tue, 13 Sep 2016 19:20:03 -0400
From:   Sinan Kaya <okaya@...eaurora.org>
To:     Bjorn Helgaas <helgaas@...nel.org>
Cc:     linux-pci@...r.kernel.org, timur@...eaurora.org,
        cov@...eaurora.org, alex.williamson@...hat.com,
        vikrams@...eaurora.org, linux-arm-msm@...r.kernel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] PCI: save and restore device state during bus reset

On 9/13/2016 5:53 PM, Bjorn Helgaas wrote:
>> +	pci_bus_restore(dev->bus);
> This path eventually writes the Bridge Control register:
> 
>   pci_reset_bridge_secondary_bus
>     pcibios_reset_secondary_bus
>       pci_reset_secondary_bus
>         pci_write_config_word(dev, PCI_BRIDGE_CONTROL, ctrl)
> 
> But I think it'd be easy to call this on a non-bridge device, and I
> don't think there's anything in the path that checks whether this is
> actually a bridge.  I wonder if we should check that somewhere, or
> maybe even change the interface so it takes a struct pci_bus instead
> of a pci_dev.
> 

I'll change it to pci_bus.

>> > +}


-- 
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.