From: Alison Schofield <alison.schofield@intel.com>
To: <mdshahid03@gmail.com>
Cc: <vishal.l.verma@intel.com>, <dave.jiang@intel.com>,
<iweiny@kernel.org>, <nvdimm@lists.linux.dev>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvdimm/pmem: Fix disk resource cleanup on initialization failure
Date: Thu, 5 Nov 2026 15:21:13 -0800 [thread overview]
Message-ID: <au0PabL2q2640uWI@aschofie-mobl2.lan> (raw)
In-Reply-To: <20261104161825.314835-1-mdshahid03@gmail.com>
On Wed, Nov 04, 2026 at 09:48:25PM +0530, mdshahid03@gmail.com wrote:
> From: Mohammad Shahid <mdshahid03@gmail.com>
>
> pmem_attach_disk() allocates a disk using blk_alloc_disk()
> before initializing badblocks.
>
> If devm_init_badblocks() fails, the function return directly
> without releasing the previously allocated disk.
>
> Use the existing cleanup path to release the disk and preserve
> the original error code returned by devm_init_badblocks().
Hi Mohammad,
Your patch looks right but this leak is fixed in v7.4-rc1 by:
855a46681e0b ("nvdimm/pmem: Release gendisk on probe failure")
Basing and building your patches on the latest tree, usually
the most recent mainline -rc before sending helps avoid this.
Sometimes a patch is also just on the mailing list, so check
the list too.
-- Alison
>
> Signed-off-by: Mohammad Shahid <mdshahid03@gmail.com>
> ---
> drivers/nvdimm/pmem.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/nvdimm/pmem.c b/drivers/nvdimm/pmem.c
> index 5fb86595e8bd..76e80eccc8e7 100644
> --- a/drivers/nvdimm/pmem.c
> +++ b/drivers/nvdimm/pmem.c
> @@ -563,8 +563,9 @@ static int pmem_attach_disk(struct device *dev,
> nvdimm_namespace_disk_name(ndns, disk->disk_name);
> set_capacity(disk, (pmem->size - pmem->pfn_pad - pmem->data_offset)
> / 512);
> - if (devm_init_badblocks(dev, &pmem->bb))
> - return -ENOMEM;
> + rc = devm_init_badblocks(dev, &pmem->bb);
> + if (rc)
> + goto out;
> nvdimm_badblocks_populate(nd_region, &pmem->bb, &bb_range);
> disk->bb = &pmem->bb;
>
> --
> 2.43.0
>
prev parent reply other threads:[~2026-11-05 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 16:18 mdshahid03
2026-11-05 23:21 ` Alison Schofield [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=au0PabL2q2640uWI@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=iweiny@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdshahid03@gmail.com \
--cc=nvdimm@lists.linux.dev \
--cc=vishal.l.verma@intel.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®