Re: [PATCH v5 01/23] PCI: Fix race condition in pci_enable/disable_device()

2019-09-30 Thread Sergey Miroshnichenko
Hello Bjorn, On 9/28/19 12:59 AM, Bjorn Helgaas wrote: On Fri, Aug 16, 2019 at 07:50:39PM +0300, Sergey Miroshnichenko wrote: This is a yet another approach to fix an old [1-2] concurrency issue, when: - two or more devices are being hot-added into a bridge which was initially empty; -

Re: [PATCH v5 01/23] PCI: Fix race condition in pci_enable/disable_device()

2019-09-27 Thread Bjorn Helgaas
On Fri, Aug 16, 2019 at 07:50:39PM +0300, Sergey Miroshnichenko wrote: > This is a yet another approach to fix an old [1-2] concurrency issue, when: > - two or more devices are being hot-added into a bridge which was >initially empty; > - a bridge with two or more devices is being hot-added;

Re: [PATCH v5 01/23] PCI: Fix race condition in pci_enable/disable_device()

2019-08-22 Thread Marta Rybczynska
- On 16 Aug, 2019, at 18:50, Sergey Miroshnichenko s.miroshniche...@yadro.com wrote: > This is a yet another approach to fix an old [1-2] concurrency issue, when: > - two or more devices are being hot-added into a bridge which was > initially empty; > - a bridge with two or more devices

[PATCH v5 01/23] PCI: Fix race condition in pci_enable/disable_device()

2019-08-16 Thread Sergey Miroshnichenko
This is a yet another approach to fix an old [1-2] concurrency issue, when: - two or more devices are being hot-added into a bridge which was initially empty; - a bridge with two or more devices is being hot-added; - during boot, if BIOS/bootloader/firmware doesn't pre-enable bridges. The