* [PATCH 5/6] driver core: cpu: Fix OF node reference leak in register_cpu() error path
@ 2026-09-15 4:35 Wentao Liang
2026-09-23 8:40 ` Sudeep Holla
0 siblings, 1 reply; 2+ messages in thread
From: Wentao Liang @ 2026-09-15 4:35 UTC (permalink / raw)
To: dakr
Cc: driver-core, gregkh, linux-kernel, rafael, rob.herring,
sudeep.holla, lkml, Wentao Liang, stable
register_cpu() assigns the device node returned by of_get_cpu_node(),
which comes with a reference, to cpu->dev.of_node. If device_register()
fails, the error path calls put_device() and returns, but nothing ever
drops the OF node reference: cpu_device_release() is empty and the
driver core does not put dev->of_node on the failure path, so each
failed registration leaks a reference on the device node.
Release the OF node with of_node_put() on the error path. It is safe
to access cpu->dev.of_node after put_device(), since the statically
allocated struct cpu is never freed by cpu_device_release().
Fixes: f86e4718f24b ("driver/core: cpu: initialize of_node in cpu's device struture")
Cc: stable@vger.kernel.org
Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
---
drivers/base/cpu.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
index 875abdc9942e..bc96725c8d4c 100644
--- a/drivers/base/cpu.c
+++ b/drivers/base/cpu.c
@@ -431,6 +431,7 @@ int register_cpu(struct cpu *cpu, int num)
error = device_register(&cpu->dev);
if (error) {
put_device(&cpu->dev);
+ of_node_put(cpu->dev.of_node);
return error;
}
--
2.34.1
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH 5/6] driver core: cpu: Fix OF node reference leak in register_cpu() error path
2026-09-15 4:35 [PATCH 5/6] driver core: cpu: Fix OF node reference leak in register_cpu() error path Wentao Liang
@ 2026-09-23 8:40 ` Sudeep Holla
0 siblings, 0 replies; 2+ messages in thread
From: Sudeep Holla @ 2026-09-23 8:40 UTC (permalink / raw)
To: Wentao Liang
Cc: dakr, driver-core, Sudeep Holla, gregkh, linux-kernel, rafael,
rob.herring, lkml, stable
On Tue, Sep 15, 2026 at 04:35:23AM +0000, Wentao Liang wrote:
> register_cpu() assigns the device node returned by of_get_cpu_node(),
> which comes with a reference, to cpu->dev.of_node. If device_register()
> fails, the error path calls put_device() and returns, but nothing ever
> drops the OF node reference: cpu_device_release() is empty and the
> driver core does not put dev->of_node on the failure path, so each
> failed registration leaks a reference on the device node.
>
> Release the OF node with of_node_put() on the error path. It is safe
> to access cpu->dev.of_node after put_device(), since the statically
> allocated struct cpu is never freed by cpu_device_release().
>
If this is part of a series, I can't find 5 other patches or the cover
letter anywhere.
> Fixes: f86e4718f24b ("driver/core: cpu: initialize of_node in cpu's device struture")
> Cc: stable@vger.kernel.org
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> drivers/base/cpu.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
> index 875abdc9942e..bc96725c8d4c 100644
> --- a/drivers/base/cpu.c
> +++ b/drivers/base/cpu.c
> @@ -431,6 +431,7 @@ int register_cpu(struct cpu *cpu, int num)
> error = device_register(&cpu->dev);
> if (error) {
> put_device(&cpu->dev);
> + of_node_put(cpu->dev.of_node);
I would also set the of_node to NULL as I see some archs like PPC is
making some decisions based on non-NULL pointer. I want to prevent any
further OF reference operations on that pointer.
--
Regards,
Sudeep
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2026-09-23 8:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-09-15 4:35 [PATCH 5/6] driver core: cpu: Fix OF node reference leak in register_cpu() error path Wentao Liang
2026-09-23 8:40 ` Sudeep Holla
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox