From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: kristen.c.accardi@intel.com, linux-pci@vger.kernel.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: pciehp resume handler - racy?
Date: Wed, 01 Jul 2009 13:34:02 +0900 [thread overview]
Message-ID: <4A4AE73A.7050907@jp.fujitsu.com> (raw)
In-Reply-To: <4A4A3697.7020804@tuffmail.co.uk>
Alan Jenkins wrote:
> Hi,
>
> I've been hacking on the PCI hotplug driver otherwise known as
> eeepc-laptop. At one point I reliably triggered a race on resume. In
> the hot-unplug case, it seemed that the resume handler would try to
> remove the PCI device at the same time as an acpi notification (run in a
> workqueue) tried to do the same thing. The result was an OOPS. My
> conclusion is that the PCI hotplug core does not protect against
> multiple simultaneous removals of the same device.
Though I don't know hotplug driver for eeepc-laptop at all, I guess
it doesn't use pci_hp_register(), which is for registering a hotplug
slot to pci hotplug core. The pci_hp_register() prevents a hot-plug
slot from being managed by multiple hotplug controller drivers at
the same time. Using pci_hp_register() would be one of the solution
for eeepc-laptop hotplug driver.
>
> pciehp appears to have an analogous problem. Assuming pciehp_force is
> set, the resume handler can hot-unplug the device. The interrupt
> handler could try to hot-unplug the device at the same time. Should the
> resume handler take the slot mutex to avoid this problem?
>
Hot-plug operations for the same hotplug slot are serialized by
crit_sect mutex of struct controller in pciehp_enable_slot() and
pciehp_disable_slot(). So I don't think multiple hot-plug
operations for the same slot would be executed at the same time.
Thanks,
Kenji Kaneshige
> diff --faked-up a/drivers/pci/hotplug/pciehp_core.c b/drivers/pci/hotplug/pciehp_core.c
> --- a/drivers/pci/hotplug/pciehp_core.c
> +++ b/drivers/pci/hotplug/pciehp_core.c
> @@ -382,15 +382,18 @@ static int pciehp_resume (struct pcie_device *dev)
> /* reinitialize the chipset's event detection logic */
> pcie_enable_notification(ctrl);
>
> t_slot = pciehp_find_slot(ctrl, ctrl->slot_device_offset);
> + mutex_lock(&t_slot->lock);
>
> /* Check if slot is occupied */
> t_slot->hpc_ops->get_adapter_status(t_slot, &status);
> if (status)
> pciehp_enable_slot(t_slot);
> else
> pciehp_disable_slot(t_slot);
> +
> + mutex_unlock(&t_slot->lock);
> }
> return 0;
> }
> #endif /* PM */
>
>
> Regards
> Alan
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
prev parent reply other threads:[~2009-07-01 4:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 16:00 pciehp resume handler - racy? Alan Jenkins
2009-07-01 4:34 ` Kenji Kaneshige [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A4AE73A.7050907@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.