From: Bjorn Helgaas <helgaas@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>
Cc: Aadityarangan Shridhar Iyengar <adiyenga@cisco.com>,
bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI/PTM: Fix memory leak in pcie_ptm_create_debugfs() error path
Date: Wed, 14 Jan 2026 10:39:57 -0600 [thread overview]
Message-ID: <20260114163957.GA815952@bhelgaas> (raw)
In-Reply-To: <pdp4xc4d5ee3e547mmdro5riui3mclduqdl7j6iclfbozo2a4c@7m3qdm6yrhuv>
On Wed, Jan 14, 2026 at 12:58:56PM +0530, Manivannan Sadhasivam wrote:
> On Sun, Jan 11, 2026 at 10:06:50PM +0530, Aadityarangan Shridhar Iyengar wrote:
> > In pcie_ptm_create_debugfs(), if devm_kasprintf() fails after successfully
> > allocating ptm_debugfs with kzalloc(), the function returns NULL without
> > freeing the allocated memory, resulting in a memory leak.
> >
> > Fix this by adding kfree(ptm_debugfs) before returning NULL in the
> > devm_kasprintf() error path.
> >
> > This leak is particularly problematic during memory pressure situations
> > where devm_kasprintf() is more likely to fail, potentially compounding
> > the memory exhaustion issue.
> >
> > Fixes: 132833405e61 ("PCI: Add debugfs support for exposing PTM context")
> > Signed-off-by: Aadityarangan Shridhar Iyengar <adiyenga@cisco.com>
> > ---
> > drivers/pci/pcie/ptm.c | 4 +++-
> > 1 file changed, 3 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/pci/pcie/ptm.c b/drivers/pci/pcie/ptm.c
> > index ed0f9691e7d1..09c0167048a3 100644
> > --- a/drivers/pci/pcie/ptm.c
> > +++ b/drivers/pci/pcie/ptm.c
> > @@ -542,8 +542,10 @@ struct pci_ptm_debugfs *pcie_ptm_create_debugfs(struct device *dev, void *pdata,
> > return NULL;
> >
> > dirname = devm_kasprintf(dev, GFP_KERNEL, "pcie_ptm_%s", dev_name(dev));
> > - if (!dirname)
> > + if (!dirname) {
> > + kfree(ptm_debugfs);
> > return NULL;
> > + }
>
> Thanks for spotting the leak. I also forgot to remove it in
> pcie_ptm_destroy_debugfs(). Since this one got applied, Bjorn could you please
> squash the below fix as well?
>
> diff --git a/drivers/pci/pcie/ptm.c b/drivers/pci/pcie/ptm.c
> index ed0f9691e7d1..2c27bee0773d 100644
> --- a/drivers/pci/pcie/ptm.c
> +++ b/drivers/pci/pcie/ptm.c
> @@ -574,6 +574,7 @@ void pcie_ptm_destroy_debugfs(struct pci_ptm_debugfs *ptm_debugfs)
>
> mutex_destroy(&ptm_debugfs->lock);
> debugfs_remove_recursive(ptm_debugfs->debugfs);
> + kfree(ptm_debugfs);
> }
> EXPORT_SYMBOL_GPL(pcie_ptm_destroy_debugfs);
> #endif
>
> For this patch,
>
> Reviewed-by: Manivannan Sadhasivam <mani@kernel.org>
Added the fix and your Reviewed-by, thanks!
next prev parent reply other threads:[~2026-01-14 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 16:36 [PATCH] PCI/PTM: Fix memory leak in pcie_ptm_create_debugfs() error path Aadityarangan Shridhar Iyengar
2026-01-13 18:59 ` Bjorn Helgaas
2026-01-14 7:28 ` Manivannan Sadhasivam
2026-01-14 16:39 ` Bjorn Helgaas [this message]
2026-01-14 16:26 ` [PATCH] PCI/AER: Fix device reference leak in aer_inject() Aadityarangan Shridhar Iyengar
-- strict thread matches above, loose matches on Subject: below --
2026-01-11 16:30 [PATCH] PCI/PTM: Fix memory leak in pcie_ptm_create_debugfs() error path Aadityarangan Shridhar Iyengar
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=20260114163957.GA815952@bhelgaas \
--to=helgaas@kernel.org \
--cc=adiyenga@cisco.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mani@kernel.org \
/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