RE: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject

2017-02-27 Thread Long Li
gt; p...@vger.kernel.org > Subject: Re: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject > > On Fri, Feb 24, 2017 at 09:49:17PM +, Long Li wrote: > > A PCI_EJECT message can arrive at the same time we are calling > pci_scan_child_bus in the workqueue for the

Re: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject

2017-02-25 Thread Greg KH
On Fri, Feb 24, 2017 at 09:49:17PM +, Long Li wrote: > A PCI_EJECT message can arrive at the same time we are calling > pci_scan_child_bus in the workqueue for the previous PCI_BUS_RELATIONS > message or in create_root_hv_pci_bus(), in this case we could potentailly > modify the bus from mul

[Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject

2017-02-24 Thread Long Li
A PCI_EJECT message can arrive at the same time we are calling pci_scan_child_bus in the workqueue for the previous PCI_BUS_RELATIONS message or in create_root_hv_pci_bus(), in this case we could potentailly modify the bus from multiple places. Properly lock the bus access. Thanks Dexuan Cui f

RE: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject

2017-01-27 Thread KY Srinivasan
g; Long Li > Subject: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject > > [This sender failed our fraud detection checks and may not be who they > appear to be. Learn about spoofing at http://aka.ms/LearnAboutSpoofing] > > From: Long Li > > A PCI_EJECT messa