Ok, I will resend. > -----Original Message----- > From: Greg KH [mailto:greg@xxxxxxxxx] > Sent: Saturday, February 25, 2017 12:02 AM > To: Long Li <longli@xxxxxxxxxxxxx> > Cc: KY Srinivasan <kys@xxxxxxxxxxxxx>; Haiyang Zhang > <haiyangz@xxxxxxxxxxxxx>; Bjorn Helgaas <bhelgaas@xxxxxxxxxx>; > devel@xxxxxxxxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; linux- > pci@xxxxxxxxxxxxxxx > 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... _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
