mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Abdun Nihaal <nihaal@cse.iitm.ac.in>
Cc: Vishal Verma <vishal.l.verma@intel.com>,
	Dan Williams <djbw@kernel.org>, Dave Jiang <dave.jiang@intel.com>,
	Ira Weiny <ira.weiny@intel.com>, <nvdimm@lists.linux.dev>,
	<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH 0/2] nvdimm/btt: fix a few memory leaks
Date: Mon, 1 Jun 2026 16:03:19 -0700	[thread overview]
Message-ID: <ah4PtzCjX6mcElt7@aschofie-mobl2.lan> (raw)
In-Reply-To: <20260519-nvdimmleaks-v1-0-592300fb7a43@cse.iitm.ac.in>

On Tue, May 19, 2026 at 11:20:11AM +0530, Abdun Nihaal wrote:
> The following two patches fix memory leak issues in error paths in the
> btt_init() and discover_arenas() functions.
> 
> - nvdimm/btt: fix potential memory leak in btt_init()
> - nvdimm/btt: fix potential memory leak in discover_arenas()
> 
> Compile tested only. Issue found using static analysis.
> 
> Signed-off-by: Abdun Nihaal <nihaal@cse.iitm.ac.in>


Hi Abdun,

Thanks for the patches!

I'm giving this my Reviewed-by Tag and will apply with some fixups
to the commit messages and the commit log of patch 2.

Sashiko noted 3 potential issues which I've worked thru to my
satisfaction (no changes needed) For future reference, I'd expect
you to come back around and offer comment on such complaints.

https://sashiko.dev/#/patchset/20260519-nvdimmleaks-v1-0-592300fb7a43%40cse.iitm.ac.in

Reviewed-by: Alison Schofield <alison.schofield@intel.com>


  parent reply	other threads:[~2026-06-01 23:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19  5:50 Abdun Nihaal
2026-05-19  5:50 ` [PATCH 1/2] nvdimm/btt: fix potential memory leak in discover_arenas() Abdun Nihaal
2026-05-19  5:50 ` [PATCH 2/2] nvdimm/btt: fix potential memory leak in btt_init() Abdun Nihaal
2026-06-01 23:03 ` Alison Schofield [this message]
2026-06-02  0:33 ` [PATCH 0/2] nvdimm/btt: fix a few memory leaks Alison Schofield

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=ah4PtzCjX6mcElt7@aschofie-mobl2.lan \
    --to=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=djbw@kernel.org \
    --cc=ira.weiny@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nihaal@cse.iitm.ac.in \
    --cc=nvdimm@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    --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®