[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20440867.YaQfKrcfsQ@vostro.rjw.lan>
Date: Fri, 10 Jan 2014 15:20:44 +0100
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Bjorn Helgaas <bhelgaas@...gle.com>
Cc: Yinghai Lu <yinghai@...nel.org>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Gu Zheng <guz.fnst@...fujitsu.com>,
Guo Chao <yan@...ux.vnet.ibm.com>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Myron Stowe <myron.stowe@...il.com>,
Benjamin Herrenschmidt <benh@....ibm.com>,
linux-scsi@...r.kernel.org, Matthew Garrett <mjg59@...f.ucam.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: [PATCH 0/9] PCI: Eliminate race conditions between hotplug and sysfs rescan/remove (Was: Re: [PATCH v2 04/10] PCI: Destroy pci dev only once)
[Cc: adding linux-scsi for the MPT changes, Ben for powerpc, Matthew for
platform/x86 and Konrad for Xen]
On Friday, December 06, 2013 02:21:50 AM Rafael J. Wysocki wrote:
[...]
>
> OK
>
> To be a bit more constructive, as the next step I'd try to use
> pci_remove_rescan_mutex to serialize all PCI hotplug operations (as I said
> above) without making the other changes made by my patch. Does that sound
> reasonable?
Well, no answer here, so as a followup, a series implementing that idea
follows.
I *hope* I found all of the places that need to be synchronized vs the bus
rescan and device removal that can be triggered via sysfs, but I might overlook
something. Also in some cases I wasn't quite sure how much stuff to put under
the lock, because said stuff is not exactly straightforward.
Enjoy!
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists