From: Tyrel Datwyler <tyreld@linux.ibm.com>
To: Daniel Axtens <dja@axtens.net>, mpe@ellerman.id.au
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/pseries: extract host bridge from pci_bus prior to bus removal
Date: Fri, 16 Apr 2021 13:21:09 -0700 [thread overview]
Message-ID: <9ff72ca1-debd-9bc5-c445-db68e673f3ef@linux.ibm.com> (raw)
In-Reply-To: <878s5ig0p7.fsf@linkitivity.dja.id.au>
On 4/16/21 12:15 AM, Daniel Axtens wrote:
> Hi Tyrel,
>
>> The pci_bus->bridge reference may no longer be valid after
>> pci_bus_remove() resulting in passing a bad value to device_unregister()
>> for the associated bridge device.
>>
>> Store the host_bridge reference in a separate variable prior to
>> pci_bus_remove().
>>
> The patch certainly seems to do what you say. I'm not really up on the
> innards of PCI, so I'm struggling to figure out by what code path
> pci_bus_remove() might invalidate pci_bus->bridge? A quick look at
> pci_remove_bus was not very illuminating but I didn't chase down every
> call it made.
remove_phb_dynamic()
|--> pci_remove_bus(bus)
|--> device_unregister(&bus->dev)
|--> put_device(dev)
|--> device_release(kobj)
|--> dev->class->dev_release(dev) == release_pci_bus(dev)
|--> kfree(bus)
We have the above call chain that takes place in the when put_device() triggers
the kobject ref count to go zero. The kobject_release function in this case is
device_release() which in turn calls dev->class->dev_release(dev). For a pci_bus
the class is appropriately pcibus_class whose dev_release() callback points to
release_pci_bus(). This in turn calls kfree() on the bus. Which means we can no
longer safely dereference any fields of the pci_bus struct.
-Tyrel
>
> Kind regards,
> Daniel
>
>> Fixes: 7340056567e3 ("powerpc/pci: Reorder pci bus/bridge unregistration during PHB removal")
>> Signed-off-by: Tyrel Datwyler <tyreld@linux.ibm.com>
>> ---
>> arch/powerpc/platforms/pseries/pci_dlpar.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/arch/powerpc/platforms/pseries/pci_dlpar.c b/arch/powerpc/platforms/pseries/pci_dlpar.c
>> index f9ae17e8a0f4..a8f9140a24fa 100644
>> --- a/arch/powerpc/platforms/pseries/pci_dlpar.c
>> +++ b/arch/powerpc/platforms/pseries/pci_dlpar.c
>> @@ -50,6 +50,7 @@ EXPORT_SYMBOL_GPL(init_phb_dynamic);
>> int remove_phb_dynamic(struct pci_controller *phb)
>> {
>> struct pci_bus *b = phb->bus;
>> + struct pci_host_bridge *host_bridge = to_pci_host_bridge(b->bridge);
>> struct resource *res;
>> int rc, i;
>>
>> @@ -76,7 +77,8 @@ int remove_phb_dynamic(struct pci_controller *phb)
>> /* Remove the PCI bus and unregister the bridge device from sysfs */
>> phb->bus = NULL;
>> pci_remove_bus(b);
>> - device_unregister(b->bridge);
>> + host_bridge->bus = NULL;
>> + device_unregister(&host_bridge->dev);
>>
>> /* Now release the IO resource */
>> if (res->flags & IORESOURCE_IO)
>> --
>> 2.27.0
next prev parent reply other threads:[~2021-04-16 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 18:24 [PATCH] powerpc/pseries: extract host bridge from pci_bus prior to bus removal Tyrel Datwyler
2021-04-13 19:04 ` Tyrel Datwyler
2021-04-16 7:15 ` Daniel Axtens
2021-04-16 20:21 ` Tyrel Datwyler [this message]
2021-04-19 4:00 ` Michael Ellerman
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=9ff72ca1-debd-9bc5-c445-db68e673f3ef@linux.ibm.com \
--to=tyreld@linux.ibm.com \
--cc=dja@axtens.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).