* + device-dax-fix-refcount-leak-in-__devm_create_dev_dax-error-path.patch added to mm-hotfixes-unstable branch
@ 2026-04-12 17:55 Andrew Morton
0 siblings, 0 replies; only message in thread
From: Andrew Morton @ 2026-04-12 17:55 UTC (permalink / raw)
To: mm-commits, vishal.l.verma, stable, dave.jiang, dan.j.williams,
lgs201920130244, akpm
The patch titled
Subject: device-dax: Fix refcount leak in __devm_create_dev_dax() error path
has been added to the -mm mm-hotfixes-unstable branch. Its filename is
device-dax-fix-refcount-leak-in-__devm_create_dev_dax-error-path.patch
This patch will shortly appear at
https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/device-dax-fix-refcount-leak-in-__devm_create_dev_dax-error-path.patch
This patch will later appear in the mm-hotfixes-unstable branch at
git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/process/submit-checklist.rst when testing your code ***
The -mm tree is included into linux-next via various
branches at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
and is updated there most days
------------------------------------------------------
From: Guangshuo Li <lgs201920130244@gmail.com>
Subject: device-dax: Fix refcount leak in __devm_create_dev_dax() error path
Date: Sun, 12 Apr 2026 15:00:10 +0800
After device_initialize(), the embedded struct device in dev_dax is
expected to be released through the device core with put_device().
In __devm_create_dev_dax(), several failure paths after
device_initialize() free dev_dax directly instead of dropping the device
reference, which bypasses the normal device core lifetime handling and
leaks the reference held on the embedded struct device.
Fix this by assigning dev->type before device_initialize(), so the release
callback is available, use put_device() in the post-initialization error
paths, and keep dev_dax range cleanup explicit since it is not handled by
dev_dax_release().
Link: https://lkml.kernel.org/r/20260412070010.2402830-1-lgs201920130244@gmail.com
Fixes: c2f3011ee697f ("device-dax: add an allocation interface for device-dax instances")
Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>
Cc: Vishal Verma <vishal.l.verma@intel.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/dax/bus.c | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
--- a/drivers/dax/bus.c~device-dax-fix-refcount-leak-in-__devm_create_dev_dax-error-path
+++ a/drivers/dax/bus.c
@@ -1453,6 +1453,7 @@ static struct dev_dax *__devm_create_dev
}
dev = &dev_dax->dev;
+ dev->type = &dev_dax_type;
device_initialize(dev);
dev_set_name(dev, "dax%d.%d", dax_region->id, dev_dax->id);
@@ -1499,7 +1500,6 @@ static struct dev_dax *__devm_create_dev
dev->devt = inode->i_rdev;
dev->bus = &dax_bus_type;
dev->parent = parent;
- dev->type = &dev_dax_type;
rc = device_add(dev);
if (rc) {
@@ -1522,14 +1522,13 @@ static struct dev_dax *__devm_create_dev
return dev_dax;
err_alloc_dax:
- kfree(dev_dax->pgmap);
err_pgmap:
free_dev_dax_ranges(dev_dax);
err_range:
- free_dev_dax_id(dev_dax);
+ put_device(dev);
+ return ERR_PTR(rc);
err_id:
kfree(dev_dax);
-
return ERR_PTR(rc);
}
_
Patches currently in -mm which might be from lgs201920130244@gmail.com are
device-dax-fix-refcount-leak-in-__devm_create_dev_dax-error-path.patch
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-04-12 17:55 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-12 17:55 + device-dax-fix-refcount-leak-in-__devm_create_dev_dax-error-path.patch added to mm-hotfixes-unstable branch Andrew Morton
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox