From: Su Hui <suhui@nfschina.com>
To: "liwei (JK)" <liwei728@huawei.com>
Cc: linux-kernel@vger.kernel.org, make24@iscas.ac.cn,
bhelgaas@google.com, linux-pci@vger.kernel.org,
bobo.shaobowang@huawei.com, wangxiongfeng2@huawei.com
Subject: Re: [PATCH] Revert "PCI: Fix reference leak in pci_register_host_bridge()"
Date: Mon, 14 Apr 2025 09:48:28 +0800 [thread overview]
Message-ID: <c6fb3f34-4296-4b86-a08c-92b16cd8e1d0@nfschina.com> (raw)
In-Reply-To: <c81b43b7-e993-4e9f-ad27-acacd0b85847@huawei.com>
On 2025/4/12 11:18, liwei (JK) wrote:
> 在 2025/4/10 19:19, Su Hui 写道:
>> On 2025/4/10 11:28, Xiangwei Li wrote:
>>> This reverts commit 804443c1f27883926de94c849d91f5b7d7d696e9.
>>>
>>> The newly added logic incorrectly sets bus_registered to true even when
>>> device_register returns an error, this is incorrect.
>>>
>>> When device_register fails, there is no need to release the
>>> reference count,
>> I think you missed some thing about device_register(). This patch is
>> wrong.
>>
>> device_register()
>> -> device_initialize()
>> -> kobject_init()
>> -> kobject_init_internal()
>> -> kref_init(&kobj->kref); //set
>> kref->refcount to 1
>> ^^^^^^^^^^^^^^^^^^^^^
>>
> Sorry, I missed the initialization of refcount in device_initialize,
> but I’m confused about the branch logic for bus_registered. Why isn’t
> free(bus) executed when bus_registered == true? My understanding is
> that the kobject_cleanup operation triggered when refcount reaches zero
> does not clean up the allocated bus. Could you clarify this further?
>
1020 dev_set_name(&bus->dev, "%04x:%02x", pci_domain_nr(bus),
bus->number);
^^^^^^^^^^^^^^^^^^^^
//device name is allocated, and should be freed when
device_register() is failed.
1021 name = dev_name(&bus->dev);
1022
1023 err = device_register(&bus->dev);
1024 bus_registered = true;
1025 if (err)
1026 goto unregister;
[...]
1117 if (bus_registered)
1118 put_device(&bus->dev);
^^^^^^^^^^^^^^^^
// decrement reference count to zero and
call release_pcibus_dev() to free bus.
// And call kfree_const() to free device
name in kobject_cleanup().
1119 else
1120 kfree(bus);
Commit 804443c1f278 fixes the memory leak of 'name' and consistent with
the annotation of device_degister():
'* NOTE: _Never_ directly free @dev after calling this function, even
* if it returned an error! Always use put_device() to give up the
* reference initialized in this function instead.'
Su Hui
next prev parent reply other threads:[~2025-04-14 1:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 3:28 Xiangwei Li
2025-04-10 11:19 ` Su Hui
2025-04-12 3:18 ` liwei (JK)
2025-04-14 1:48 ` Su Hui [this message]
2025-04-14 2:41 ` liwei (JK)
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=c6fb3f34-4296-4b86-a08c-92b16cd8e1d0@nfschina.com \
--to=suhui@nfschina.com \
--cc=bhelgaas@google.com \
--cc=bobo.shaobowang@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liwei728@huawei.com \
--cc=make24@iscas.ac.cn \
--cc=wangxiongfeng2@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
all inboxes | Powered by JetHome®