From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Jiang Liu <liuj97@gmail.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Jiang Liu <jiang.liu@huawei.com>,
Yijing Wang <wangyijing@huawei.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>
Subject: Re: [PATCH v3 2/6] PCI: split registration of PCI bus devices into two stages
Date: Wed, 09 Jan 2013 00:29:50 +0100 [thread overview]
Message-ID: <31602902.kR8ehd6tSR@vostro.rjw.lan> (raw)
In-Reply-To: <1357663945-16054-3-git-send-email-jiang.liu@huawei.com>
On Wednesday, January 09, 2013 12:52:21 AM Jiang Liu wrote:
> When handling BUS_NOTIFY_ADD_DEVICE event for a PCI bridge device,
> the notification handler can't hold reference count to the new PCI bus
> because the device object for the new bus (pci_dev->subordinate->dev)
> hasn't been initialized yet.
>
> Split the registration of PCI bus device into two stages as below,
> so that the event handler could hold reference count to the new PCI bus
> when handling BUS_NOTIFY_ADD_DEVICE event.
>
> 1) device_initialize(&pci_dev->dev)
> 2) device_initialize(&pci_dev->subordinate->dev)
> 3) notify BUS_NOTIFY_ADD_DEVICE event for pci_dev
> 4) device_add(&pci_dev->dev)
> 5) device_add(&pci_dev->subordinate->dev)
>
> Signed-off-by: Jiang Liu <jiang.liu@huawei.com>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> ---
> drivers/pci/bus.c | 2 +-
> drivers/pci/probe.c | 4 +++-
> drivers/pci/remove.c | 10 +++++-----
> 3 files changed, 9 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/pci/bus.c b/drivers/pci/bus.c
> index ad6a8b6..2fea481 100644
> --- a/drivers/pci/bus.c
> +++ b/drivers/pci/bus.c
> @@ -198,7 +198,7 @@ int pci_bus_add_child(struct pci_bus *bus)
> if (bus->bridge)
> bus->dev.parent = bus->bridge;
>
> - retval = device_register(&bus->dev);
> + retval = device_add(&bus->dev);
> if (retval)
> return retval;
>
> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
> index e557d6f..a8315c2 100644
> --- a/drivers/pci/probe.c
> +++ b/drivers/pci/probe.c
> @@ -642,6 +642,7 @@ static struct pci_bus *pci_alloc_child_bus(struct pci_bus *parent,
> */
> child->dev.class = &pcibus_class;
> dev_set_name(&child->dev, "%04x:%02x", pci_domain_nr(child), busnr);
> + device_initialize(&child->dev);
>
> /*
> * Set up the primary, secondary and subordinate
> @@ -1678,7 +1679,8 @@ struct pci_bus *pci_create_root_bus(struct device *parent, int bus,
> b->dev.class = &pcibus_class;
> b->dev.parent = b->bridge;
> dev_set_name(&b->dev, "%04x:%02x", pci_domain_nr(b), bus);
> - error = device_register(&b->dev);
> + device_initialize(&b->dev);
> + error = device_add(&b->dev);
Well, the change here isn't really necessary, as far as I can say.
> if (error)
> goto class_dev_reg_err;
>
> diff --git a/drivers/pci/remove.c b/drivers/pci/remove.c
> index fc38c48..a1fdd0f 100644
> --- a/drivers/pci/remove.c
> +++ b/drivers/pci/remove.c
> @@ -48,11 +48,11 @@ void pci_remove_bus(struct pci_bus *bus)
> list_del(&bus->node);
> pci_bus_release_busn_res(bus);
> up_write(&pci_bus_sem);
> - if (!bus->is_added)
> - return;
> -
> - pci_remove_legacy_files(bus);
> - device_unregister(&bus->dev);
> + if (bus->is_added) {
> + pci_remove_legacy_files(bus);
> + device_del(&bus->dev);
> + }
> + put_device(&bus->dev);
> }
> EXPORT_SYMBOL(pci_remove_bus);
>
>
Apart from the above
Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-01-08 23:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 14:29 [PATCH v3 1/7] PCI: make PCI device create/destroy logic symmetric Jiang Liu
2012-09-25 14:29 ` [PATCH v3 2/7] PCI: split registration of PCI bus devices into two stages Jiang Liu
2012-09-25 14:29 ` [PATCH v3 3/7] ACPI/pci_bind: correctly update binding relationship for PCI hotplug Jiang Liu
2013-01-08 0:05 ` Bjorn Helgaas
2013-01-08 16:52 ` [PATCH v3 0/6] Update PCI notification patchset to latest kernel version Jiang Liu
2013-01-08 18:30 ` Yinghai Lu
2013-01-09 9:11 ` Yijing Wang
2013-01-08 16:52 ` [PATCH v3 1/6] PCI: make PCI device create/destroy logic symmetric Jiang Liu
2013-01-08 16:52 ` [PATCH v3 2/6] PCI: split registration of PCI bus devices into two stages Jiang Liu
2013-01-08 23:29 ` Rafael J. Wysocki [this message]
2013-01-09 16:10 ` Jiang Liu
2013-01-08 16:52 ` [PATCH v3 3/6] ACPI/pci_slot: update PCI slot information when PCI hotplug event happens Jiang Liu
2013-01-09 0:01 ` Rafael J. Wysocki
2013-01-09 16:58 ` Jiang Liu
2013-01-09 20:19 ` Rafael J. Wysocki
2013-01-09 20:44 ` Bjorn Helgaas
2013-01-09 21:00 ` Rafael J. Wysocki
2013-01-10 21:24 ` Myron Stowe
2013-01-10 21:50 ` Rafael J. Wysocki
2013-01-10 23:03 ` Yinghai Lu
2013-01-10 23:39 ` Rafael J. Wysocki
2013-01-10 23:40 ` Yinghai Lu
2013-01-10 23:59 ` Rafael J. Wysocki
2013-01-11 18:06 ` Bjorn Helgaas
2013-01-11 20:46 ` Rafael J. Wysocki
2013-01-11 11:07 ` Martin Mokrejs
2013-01-11 12:07 ` Rafael J. Wysocki
2013-01-08 16:52 ` [PATCH v3 4/6] PCI/acpiphp: update ACPI hotplug slot information when PCI hotplug happens Jiang Liu
2013-01-09 0:04 ` Rafael J. Wysocki
2013-01-09 16:29 ` Jiang Liu
2013-01-09 20:23 ` Rafael J. Wysocki
2013-01-13 15:13 ` Jiang Liu
2013-01-13 20:33 ` Rafael J. Wysocki
2013-01-08 16:52 ` [PATCH v3 5/6] PCI/acpiphp: serialize access to the bridge_list list Jiang Liu
2013-01-08 16:52 ` [PATCH v3 6/6] PCI/AER: update AER configuration when PCI hotplug event happens Jiang Liu
2012-09-25 14:29 ` [PATCH v3 4/7] ACPI/pci-bind: remove bind/unbind callbacks from acpi_device_ops Jiang Liu
2012-09-25 14:29 ` [PATCH v3 5/7] ACPI/pci_slot: update PCI slot information when PCI hotplug event happens Jiang Liu
2012-09-25 14:29 ` [PATCH v3 6/7] PCI/acpiphp: update ACPI hotplug slot information when PCI hotplug happens Jiang Liu
2012-09-25 14:29 ` [PATCH v3 7/7] PCI/acpiphp: serialize access to the bridge_list list Jiang Liu
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=31602902.kR8ehd6tSR@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=bhelgaas@google.com \
--cc=jiang.liu@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=wangyijing@huawei.com \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®