NVDIMM Device and Persistent Memory development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Wentao Liang" <vulab@iscas.ac.cn>
Cc: nvdimm@lists.linux.dev
Subject: Re: [PATCH] nvdimm/bus: Fix dev double put in nd_async_device_register()
Date: Thu, 17 Sep 2026 12:44:32 +0000	[thread overview]
Message-ID: <20260917124432.B0E511F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917122816.2151081-1-vulab@iscas.ac.cn>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] nvdimm: memory leak on device_add() failure in nd_async_device_register()
--

commit 3bb889471cc9122db778cd1b964d9131ca101b98
Author: Wentao Liang <vulab@iscas.ac.cn>

nvdimm/bus: Fix dev double put in nd_async_device_register()

device_add() takes and drops its own reference on every return path, so
the async worker only owns the reference that __nd_device_register()
took with get_device(). The failure branch drops that same reference once
more before the unconditional put_device(), which underflows the refcount
and frees the device while it is still referenced by its creator.

> diff --git a/drivers/nvdimm/bus.c b/drivers/nvdimm/bus.c
> index 45b7d756e39a0..a1f33a03aba81 100644
> --- a/drivers/nvdimm/bus.c
> +++ b/drivers/nvdimm/bus.c
> @@ -488,10 +488,8 @@ static void nd_async_device_register(void *d, async_cookie_t cookie)
>  	struct device *dev = d;
>  	struct device *parent = dev->parent;
>  
> -	if (device_add(dev) != 0) {
> +	if (device_add(dev) != 0)
>  		dev_err(dev, "%s: failed\n", __func__);
> -		put_device(dev);
> -	}

[Severity: Medium]
Will this lead to a memory leak of the device if device_add() fails?

Devices initialized with device_initialize() start with a refcount of 1.
In __nd_device_register(), a second reference is taken before queuing the
async worker. If device_add() fails here, it does not consume a reference.

By removing the extra put_device() from the failure path, the async worker
only drops the second reference, leaving the device with a refcount of 1.
Because device_add() failed, the device isn't added to the parent's
klist_children, so it won't be unregistered when the parent is removed.
Since the creator simply nullifies its pointer without dropping the final
reference, does this result in a permanent leak of the device and its
container structures?

>  	put_device(dev);
>  	if (parent)
>  		put_device(parent);

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260917122816.2151081-1-vulab@iscas.ac.cn?part=1

      reply	other threads:[~2026-09-17 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 12:28 [PATCH] nvdimm/bus: Fix dev double put in nd_async_device_register() Wentao Liang
2026-09-17 12:44 ` sashiko-bot [this message]

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=20260917124432.B0E511F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vulab@iscas.ac.cn \
    /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