From: Bjorn Helgaas <bhelgaas@google.com>
To: Yijing Wang <wangyijing@huawei.com>
Cc: linux-pci@vger.kernel.org, Rajat Jain <rajatja@google.com>,
Guenter Roeck <linux@roeck-us.net>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] PCI: Use a local mutex instead of pci_bus_sem to avoid deadlock
Date: Thu, 16 Jul 2015 10:25:48 -0500 [thread overview]
Message-ID: <20150716152548.GD25591@google.com> (raw)
In-Reply-To: <55A76361.8070604@huawei.com>
On Thu, Jul 16, 2015 at 03:55:13PM +0800, Yijing Wang wrote:
> On 2015/7/16 12:22, Bjorn Helgaas wrote:
> > [+cc Guenter, Rafael]
> >
> > On Thu, Jun 11, 2015 at 07:12:14PM +0800, Yijing Wang wrote:
> >> Rajat Jain reported a deadlock when a hierarchical hot plug
> >> thread and aer recovery thread both run.
> >> https://lkml.org/lkml/2015/3/11/861
> >>
> >> thread 1:
> >> pciehp_enable_slot()
> >> pciehp_configure_device()
> >> pci_bus_add_devices()
> >> device_attach(dev)
> >> device_lock(dev) //acquire device mutex successfully
> >> ...
> >> pciehp_probe(dev)
> >> __pci_hp_register()
> >> pci_create_slot()
> >> down_write(pci_bus_sem) //deadlock here
> >>
> >> thread 2:
> >> aer_isr_one_error()
> >> aer_process_err_device()
> >> do_recovery()
> >> broadcast_error_message()
> >> pci_walk_bus()
> >> down_read(&pci_bus_sem) //acquire pci_bus_sem successfully
> >> report_error_detected(dev)
> >> device_lock(dev) // deadlock here
> >>
> >> Now we use pci_bus_sem to protect pci_slot creation and destroy,
> >> it's unnecessary. We could introduce a new local mutex instead of
> >> pci_bus_sem to avoid the deadlock.
> >
> > I see there's definitely a problem here, and using a new mutex instead of
> > pci_bus_sem certainly avoids the deadlock.
> >
> > I'm trying to convince myself that it is safe. I think we need to protect:
> >
> > - search of bus->slots list in get_slot()
> > - addition to bus->slots list in pci_create_slot()
> > - search of bus->devices list in pci_create_slot()
> > - search of bus->devices list in pci_slot_release()
> > - deletion from bus->slots list in pci_slot_release()
> >
> > Most other maintenance of these lists is protected by pci_bus_sem, so using
> > a different mutex here seems like a problem.
> >
> > If I'm mistaken, please correct me and explain why this patch is safe.
>
> Hi Bjorn, I think pci_bus_sem here was introduced to protect the bus->slots list, because it
> use down_write() here, for bus->devices list, we only traverse it, won't add/remove it, for the latter, down_read() is enough.
> When I posted this patch, I thought we should protect the bus when we start to register a slot,
> something like a big lock at outermost routine to tell others not to touch its children devices, use pci_bus_sem to protect hotplug
> cases is not a good idea, and actually in PCI code, we have found several deadlock caused by the pci_bus_sem.
>
> But for this patch, I know what you worried, what about add a down_read(&pci_bus_sem) to avoid to introduce a regression ?
>
>
> diff --git a/drivers/pci/slot.c b/drivers/pci/slot.c
> index 396c200..a9079d9 100644
> --- a/drivers/pci/slot.c
> +++ b/drivers/pci/slot.c
> @@ -14,6 +14,7 @@
>
> struct kset *pci_slots_kset;
> EXPORT_SYMBOL_GPL(pci_slots_kset);
> +static DEFINE_MUTEX(pci_slot_mutex);
>
> static ssize_t pci_slot_attr_show(struct kobject *kobj,
> struct attribute *attr, char *buf)
> @@ -106,9 +107,11 @@ static void pci_slot_release(struct kobject *kobj)
> dev_dbg(&slot->bus->dev, "dev %02x, released physical slot %s\n",
> slot->number, pci_slot_name(slot));
>
> + down_read(&pci_bus_sem);
> list_for_each_entry(dev, &slot->bus->devices, bus_list)
> if (PCI_SLOT(dev->devfn) == slot->number)
> dev->slot = NULL;
> + up_read(&pci_bus_sem);
>
> list_del(&slot->list);
This list_del() updates the bus->slots list.
> @@ -195,7 +198,7 @@ static struct pci_slot *get_slot(struct pci_bus *parent, int slot_nr)
> {
> struct pci_slot *slot;
> /*
> - * We already hold pci_bus_sem so don't worry
> + * We already hold pci_slot_mutex so don't worry
> */
> list_for_each_entry(slot, &parent->slots, list)
> if (slot->number == slot_nr) {
> @@ -253,7 +256,7 @@ struct pci_slot *pci_create_slot(struct pci_bus *parent, int slot_nr,
> int err = 0;
> char *slot_name = NULL;
>
> - down_write(&pci_bus_sem);
> + mutex_lock(&pci_slot_mutex);
>
> if (slot_nr == -1)
> goto placeholder;
> @@ -301,16 +304,18 @@ placeholder:
> INIT_LIST_HEAD(&slot->list);
> list_add(&slot->list, &parent->slots);
>
> + down_read(&pci_bus_sem);
> list_for_each_entry(dev, &parent->devices, bus_list)
> if (PCI_SLOT(dev->devfn) == slot_nr)
> dev->slot = slot;
> + up_read(&pci_bus_sem);
>
> dev_dbg(&parent->dev, "dev %02x, created physical slot %s\n",
> slot_nr, pci_slot_name(slot));
>
> out:
> kfree(slot_name);
> - up_write(&pci_bus_sem);
> + mutex_unlock(&pci_slot_mutex);
> return slot;
> err:
> kfree(slot);
> @@ -332,9 +337,9 @@ void pci_destroy_slot(struct pci_slot *slot)
> dev_dbg(&slot->bus->dev, "dev %02x, dec refcount to %d\n",
> slot->number, atomic_read(&slot->kobj.kref.refcount) - 1);
>
> - down_write(&pci_bus_sem);
> + mutex_lock(&pci_slot_mutex);
> kobject_put(&slot->kobj);
> - up_write(&pci_bus_sem);
> + mutex_unlock(&pci_slot_mutex);
> }
> EXPORT_SYMBOL_GPL(pci_destroy_slot);
next prev parent reply other threads:[~2015-07-16 15:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 11:12 [PATCH] PCI: Use a local mutex instead of pci_bus_sem to avoid deadlock Yijing Wang
2015-06-12 8:20 ` Yijing Wang
2015-06-12 18:13 ` Rajat Jain
2015-06-12 18:19 ` Rajat Jain
[not found] ` <CAA93t1ooSY2keDigmUPpO7LzvT12YwQjpxH0b1xA508LL+VWdg@mail.gmail.com>
2015-06-12 18:20 ` Guenter Roeck
2015-06-15 0:40 ` Yijing Wang
2015-06-27 3:05 ` Yijing Wang
2015-06-27 3:19 ` Guenter Roeck
2015-06-27 3:37 ` Yijing Wang
2015-07-16 4:22 ` Bjorn Helgaas
2015-07-16 7:55 ` Yijing Wang
2015-07-16 15:25 ` Bjorn Helgaas [this message]
2015-07-17 1:14 ` Yijing Wang
2015-07-17 1:35 ` Bjorn Helgaas
2015-07-17 1:54 ` Yijing Wang
2015-07-17 2:05 ` Bjorn Helgaas
2015-07-17 2:24 ` Yijing Wang
2015-07-17 2:46 ` Bjorn Helgaas
2015-07-17 2:52 ` Yijing Wang
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=20150716152548.GD25591@google.com \
--to=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rajatja@google.com \
--cc=rjw@rjwysocki.net \
--cc=wangyijing@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).