[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <BN3PR03MB22271398236EE893B6AB53BACE570@BN3PR03MB2227.namprd03.prod.outlook.com>
Date: Mon, 27 Feb 2017 21:51:46 +0000
From: Long Li <longli@...rosoft.com>
To: Greg KH <greg@...ah.com>
CC: KY Srinivasan <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: RE: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject
Ok, I will resend.
> -----Original Message-----
> From: Greg KH [mailto:greg@...ah.com]
> Sent: Saturday, February 25, 2017 12:02 AM
> To: Long Li <longli@...rosoft.com>
> Cc: KY Srinivasan <kys@...rosoft.com>; Haiyang Zhang
> <haiyangz@...rosoft.com>; Bjorn Helgaas <bhelgaas@...gle.com>;
> devel@...uxdriverproject.org; linux-kernel@...r.kernel.org; linux-
> pci@...r.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 +0000, 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 multiple places. Properly lock the bus access.
>
> Properly wrap your changelog comments at 72 columns like your editor is
> telling you to do...
Powered by blists - more mailing lists