From: Amos Kong <akong@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-pci@vger.kernel.org, seabios@seabios.org,
qemu-devel@nongnu.org, jbarnes@virtuousgeek.org,
alex.williamson@redhat.com, kevin@koconnor.net,
Jiang Liu <liuj97@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v3] pci: clean all funcs when hot-removing multifunc device
Date: Fri, 11 May 2012 08:24:18 +0800 [thread overview]
Message-ID: <4FAC5C32.9080009@redhat.com> (raw)
In-Reply-To: <4FAC5518.5060807@redhat.com>
On 05/11/2012 07:54 AM, Amos Kong wrote:
> On 05/11/2012 02:55 AM, Michael S. Tsirkin wrote:
>> On Fri, May 11, 2012 at 01:09:13AM +0800, Jiang Liu wrote:
>>> On 05/10/2012 11:44 PM, Amos Kong wrote:
>>>
>>>> diff --git a/drivers/pci/hotplug/acpiphp_glue.c b/drivers/pci/hotplug/acpiphp_glue.c
>>>> index 806c44f..a7442d9 100644
>>>> --- a/drivers/pci/hotplug/acpiphp_glue.c
>>>> +++ b/drivers/pci/hotplug/acpiphp_glue.c
>>>> @@ -885,7 +885,7 @@ static void disable_bridges(struct pci_bus *bus)
>>>> static int disable_device(struct acpiphp_slot *slot)
>>>> {
>>>> struct acpiphp_func *func;
>>>> - struct pci_dev *pdev;
>>>> + struct pci_dev *pdev, *tmp;
>>>> struct pci_bus *bus = slot->bridge->pci_bus;
>>>>
>>>> /* The slot will be enabled when func 0 is added, so check
>>>> @@ -902,9 +902,10 @@ static int disable_device(struct acpiphp_slot *slot)
>>>> func->bridge = NULL;
>>>> }
>>>>
>>>> - pdev = pci_get_slot(slot->bridge->pci_bus,
>>>> - PCI_DEVFN(slot->device, func->function));
>>>> - if (pdev) {
>>>> + list_for_each_entry_safe(pdev, tmp, &bus->devices, bus_list) {
>>>> + if (PCI_SLOT(pdev->devfn) != slot->device)
>>>> + continue;
>>>> +
>>> The pci_bus_sem lock should be acquired when walking the bus->devices list.
>>> Otherwise it may cause invalid memory access if another thread is modifying
>>> the bus->devices list concurrently.
pci_bus_sem lock is only request for writing &bus->devices list, right ?
and this protection already exists in pci_destory_dev().
static int disable_device(struct acpiphp_slot *slot)
\_ list_for_each_entry_safe(pdev, tmp, &bus->devices, bus_list) {
\_ __pci_remove_bus_device(pdev);
\_ pci_destroy_dev(dev);
static void pci_destroy_dev(struct pci_dev *dev)
{
/* Remove the device from the device lists, and prevent any further
* list accesses from this device */
down_write(&pci_bus_sem);
list_del(&dev->bus_list);
dev->bus_list.next = dev->bus_list.prev = NULL;
up_write(&pci_bus_sem);
...
}
--
Amos.
next prev parent reply other threads:[~2012-05-11 0:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1315976141-6684-1-git-send-email-akong@redhat.com>
2012-05-09 15:25 ` [Qemu-devel] [PATCH v2] pci: clean all funcs when hot-removing multifunc device Amos Kong
2012-05-10 15:44 ` [Qemu-devel] [PATCH v3] " Amos Kong
2012-05-10 17:09 ` Jiang Liu
2012-05-10 18:55 ` Michael S. Tsirkin
2012-05-10 23:54 ` Amos Kong
2012-05-11 0:24 ` Amos Kong [this message]
2012-05-11 14:00 ` Jiang Liu
2012-05-16 15:26 ` Bjorn Helgaas
2012-05-20 2:31 ` [Qemu-devel] [PATCH v4] " kongjianjun
2012-05-20 2:36 ` [Qemu-devel] [PATCH v3] " Amos Kong
2012-05-20 2:59 ` [Qemu-devel] [PATCH v5] " kongjianjun
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=4FAC5C32.9080009@redhat.com \
--to=akong@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jbarnes@virtuousgeek.org \
--cc=kevin@koconnor.net \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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 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).