Helgaas <bhelg...@google.com>;
> de...@linuxdriverproject.org; linux-kernel@vger.kernel.org; linux-
> 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:
> >
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 fo
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
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
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
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
de...@linuxdriverproject.org; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Long Li <lon...@microsoft.com>
> 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.
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
ang Zhang
> <haiya...@microsoft.com>; Bjorn Helgaas <bhelg...@google.com>
> Cc: de...@linuxdriverproject.org; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: RE: [PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject
>
>
>
> > -Original M
lgaas
> Cc: de...@linuxdriverproject.org; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: RE: [PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject
>
>
>
> > -Original Message-
> > From: Long Li
> > Sent: Monday, October 3, 2016 11:43 P
ux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Long Li <lon...@microsoft.com>
> Subject: [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/Le
> -Original Message-
> From: Long Li
> Sent: Monday, October 3, 2016 11:43 PM
> To: KY Srinivasan ; Haiyang Zhang
> ; Bjorn Helgaas
> Cc: de...@linuxdriverproject.org; linux-...@vger.kernel.org; linux-
> ker...@vger.kernel.org; Long Li
> Subject: [PATCH 2/2 v3]
From: 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
From: 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.
14 matches
Mail list logo