Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1588087
| From | Greg KH <greg@kroah.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject |
| Date | 2017-02-25 09:20 +0100 |
| Message-ID | <teFKa-4VJ-7@gated-at.bofh.it> (permalink) |
| References | <tevUt-6cZ-21@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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...
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject Long Li <longli@microsoft.com> - 2017-02-24 22:50 +0100
Re: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject Greg KH <greg@kroah.com> - 2017-02-25 09:20 +0100
RE: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject Long Li <longli@microsoft.com> - 2017-02-27 23:00 +0100
csiph-web