arch/sparc/kernel/chmc.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
From: Siyang Liu <1972843537@qq.com>
In the jbusmc_probe function, the device node mem_node fetched
via of_find_node_by_path("/memory") is not properly freed
on all code paths.
This can lead to leakage of device node reference counts,
which may result in kernel resources not being released.
This issue was detected by rule based static tools
developed by Tencent.
Signed-off-by: Siyang Liu <1972843537@qq.com>
---
arch/sparc/kernel/chmc.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/sparc/kernel/chmc.c b/arch/sparc/kernel/chmc.c
index d4c74d6b2e1b..fd20e4ee0971 100644
--- a/arch/sparc/kernel/chmc.c
+++ b/arch/sparc/kernel/chmc.c
@@ -412,7 +412,7 @@ static int jbusmc_probe(struct platform_device *op)
mem_regs = of_get_property(mem_node, "reg", &len);
if (!mem_regs) {
printk(KERN_ERR PFX "Cannot get reg property of /memory node.\n");
- goto out;
+ goto out_put;
}
num_mem_regs = len / sizeof(*mem_regs);
@@ -420,7 +420,7 @@ static int jbusmc_probe(struct platform_device *op)
p = kzalloc(sizeof(*p), GFP_KERNEL);
if (!p) {
printk(KERN_ERR PFX "Cannot allocate struct jbusmc.\n");
- goto out;
+ goto out_put;
}
INIT_LIST_HEAD(&p->list);
@@ -473,6 +473,10 @@ static int jbusmc_probe(struct platform_device *op)
err = 0;
+out_put:
+ of_node_put(mem_node);
+ goto out;
+
out:
return err;
@@ -481,7 +485,7 @@ static int jbusmc_probe(struct platform_device *op)
out_free:
kfree(p);
- goto out;
+ goto out_put;
}
/* Does BANK decode PHYS_ADDR? */
--
2.43.5
On 21/07/2025 05:57, jackysliu wrote: > From: Siyang Liu <1972843537@qq.com> > > In the jbusmc_probe function, the device node mem_node fetched > via of_find_node_by_path("/memory") is not properly freed > on all code paths. > This can lead to leakage of device node reference counts, > which may result in kernel resources not being released. Please wrap commit message according to Linux coding style / submission process (neither too early nor over the limit): https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597 Do not attach (thread) your patchsets to some other threads (unrelated or older versions). This buries them deep in the mailbox and might interfere with applying entire sets. > > This issue was detected by rule based static tools > developed by Tencent. What tools? This must be specific, give their name. Previously Tencent reports were often bogus or low quality. > > Signed-off-by: Siyang Liu <1972843537@qq.com> > --- > arch/sparc/kernel/chmc.c | 10 +++++++--- > 1 file changed, 7 insertions(+), 3 deletions(-) > > diff --git a/arch/sparc/kernel/chmc.c b/arch/sparc/kernel/chmc.c > index d4c74d6b2e1b..fd20e4ee0971 100644 > --- a/arch/sparc/kernel/chmc.c > +++ b/arch/sparc/kernel/chmc.c > @@ -412,7 +412,7 @@ static int jbusmc_probe(struct platform_device *op) > mem_regs = of_get_property(mem_node, "reg", &len); > if (!mem_regs) { > printk(KERN_ERR PFX "Cannot get reg property of /memory node.\n"); > - goto out; > + goto out_put; You did not implement at all what I asked. I wanted the code to be simpler, you just made it more complicated. Read again previous feedback. Best regards, Krzysztof
…> This can lead to leakage of device node reference counts, > which may result in kernel resources not being released. … See also one more: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16-rc6#n94 * Will you become more interested in additional tags (like “Fixes” and “Cc”)? * Would the subsystem specification “sparc” be more appropriate in the summary phrase? …> --- > arch/sparc/kernel/chmc.c | 10 +++++++--- … How do you think about to improve your version management? https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16-rc6#n784 Regards, Markus
From: Siyang Liu <1972843537@qq.com>
In the jbusmc_probe function, the device node mem_node fetched
via of_find_node_by_path("/memory") is not properly freed
on all code paths.
This can lead to leakage of device node reference counts,
which may result in kernel resources not being released.
This issue was detected by rule based static tools
developed by Tencent.
Fixes: e70140ba0d2b ("Get rid of 'remove_new' relic from platform driver struct")
Signed-off-by: Siyang Liu <1972843537@qq.com>
---
arch/sparc/kernel/chmc.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/arch/sparc/kernel/chmc.c b/arch/sparc/kernel/chmc.c
index d4c74d6b2e1b..fd20e4ee0971 100644
--- a/arch/sparc/kernel/chmc.c
+++ b/arch/sparc/kernel/chmc.c
@@ -412,7 +412,7 @@ static int jbusmc_probe(struct platform_device *op)
mem_regs = of_get_property(mem_node, "reg", &len);
if (!mem_regs) {
printk(KERN_ERR PFX "Cannot get reg property of /memory node.\n");
- goto out;
+ goto out_put;
}
num_mem_regs = len / sizeof(*mem_regs);
@@ -420,7 +420,7 @@ static int jbusmc_probe(struct platform_device *op)
p = kzalloc(sizeof(*p), GFP_KERNEL);
if (!p) {
printk(KERN_ERR PFX "Cannot allocate struct jbusmc.\n");
- goto out;
+ goto out_put;
}
INIT_LIST_HEAD(&p->list);
@@ -473,6 +473,10 @@ static int jbusmc_probe(struct platform_device *op)
err = 0;
+out_put:
+ of_node_put(mem_node);
+ goto out;
+
out:
return err;
@@ -481,7 +485,7 @@ static int jbusmc_probe(struct platform_device *op)
out_free:
kfree(p);
- goto out;
+ goto out_put;
}
/* Does BANK decode PHYS_ADDR? */
--
2.43.5
On 21/07/2025 09:55, jackysliu wrote: > From: Siyang Liu <1972843537@qq.com> > > In the jbusmc_probe function, the device node mem_node fetched > via of_find_node_by_path("/memory") is not properly freed > on all code paths. > This can lead to leakage of device node reference counts, > which may result in kernel resources not being released. > > This issue was detected by rule based static tools > developed by Tencent. > > Fixes: e70140ba0d2b ("Get rid of 'remove_new' relic from platform driver struct") > > Signed-off-by: Siyang Liu <1972843537@qq.com> > --- > arch/sparc/kernel/chmc.c | 10 +++++++--- > 1 file changed, 7 insertions(+), 3 deletions(-) > > diff --git a/arch/sparc/kernel/chmc.c b/arch/sparc/kernel/chmc.c > index d4c74d6b2e1b..fd20e4ee0971 100644 > --- a/arch/sparc/kernel/chmc.c > +++ b/arch/sparc/kernel/chmc.c > @@ -412,7 +412,7 @@ static int jbusmc_probe(struct platform_device *op) > mem_regs = of_get_property(mem_node, "reg", &len); > if (!mem_regs) { > printk(KERN_ERR PFX "Cannot get reg property of /memory node.\n"); > - goto out; > + goto out_put; Nothing improved. You just ignored all the comments. Best regards, Krzysztof
…> --- > arch/sparc/kernel/chmc.c | 10 +++++++--- … Why did you overlook mentioned patch requirements once more? https://lore.kernel.org/all/?q=%22This+looks+like+a+new+version+of+a+previously+submitted+patch%22 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.16-rc6#n784 Regards, Markus
© 2016 - 2025 Red Hat, Inc.