From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Michael Walle <michael@walle.cc>,
linux-kernel@vger.kernel.org,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <pratyush@kernel.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v4] mtd: spi-nor: fix memory leak when using debugfs_lookup()
Date: Mon, 6 Mar 2023 12:05:58 +0100 [thread overview]
Message-ID: <20230306120558.00f614fb@xps-13> (raw)
In-Reply-To: <ZAWuvRHVVV3hTm0e@kroah.com>
Hi Greg,
gregkh@linuxfoundation.org wrote on Mon, 6 Mar 2023 10:13:33 +0100:
> On Mon, Mar 06, 2023 at 09:33:36AM +0100, Miquel Raynal wrote:
> > Hi Greg,
> >
> > gregkh@linuxfoundation.org wrote on Mon, 6 Mar 2023 07:52:38 +0100:
> >
> > > On Wed, Feb 08, 2023 at 05:15:41PM +0100, Michael Walle wrote:
> > > > Am 2023-02-08 17:02, schrieb Greg Kroah-Hartman:
> > > > > When calling debugfs_lookup() the result must have dput() called on it,
> > > > > otherwise the memory will leak over time. To solve this, remove the
> > > > > lookup and create the directory on the first device found, and then
> > > > > remove it when the module is unloaded.
> > > > >
> > > > > Cc: Tudor Ambarus <tudor.ambarus@microchip.com>
> > > > > Cc: Pratyush Yadav <pratyush@kernel.org>
> > > > > Cc: Michael Walle <michael@walle.cc>
> > > > > Cc: Miquel Raynal <miquel.raynal@bootlin.com>
> > > > > Cc: Richard Weinberger <richard@nod.at>
> > > > > Cc: Vignesh Raghavendra <vigneshr@ti.com>
> > > > > Cc: linux-mtd@lists.infradead.org
> > > > > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > >
> > > > Reviewed-by: Michael Walle <michael@walle.cc>
> > > >
> > > > one nit below I didn't notice earlier, no need to send a new
> > > > patch version just for that.
> > > >
> > > > ..
> > > >
> > > > > +void spi_nor_debugfs_shutdown(void)
> > > > > +{
> > > > > + if (rootdir)
> > > > > + debugfs_remove(rootdir);
> > > >
> > > > debugfs_remove() already has a check for NULL.
> > > >
> > >
> > > Ah, good catch, I merged this in when I applied it to my tree, thanks!
> >
> > Any reasons why you did apply this patch to your tree? It is a spi-nor
> > fix, I would have expected it to go through mtd.
>
> It's been sitting around for a month, I assumed it was lost, so I picked
> it up.
Sorry if it took too long, the merge window also happened during that
time, we are collecting patches now that 6.3-rc1 has been released.
Next time don't hesitate to ping first ;-)
> I can revert it if you don't want me to take it for 6.3-final
> through my driver core tree.
I'll let spi-nor maintainers decide what they prefer.
Thanks,
Miquèl
next prev parent reply other threads:[~2023-03-06 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 16:02 [PATCH v4] mtd: spi-nor: fix memory leak when using debugfs_lookup() Greg Kroah-Hartman
2023-02-08 16:15 ` Michael Walle
2023-02-08 17:30 ` Greg Kroah-Hartman
2023-03-06 6:52 ` Greg Kroah-Hartman
2023-03-06 8:33 ` Miquel Raynal
2023-03-06 9:13 ` Greg Kroah-Hartman
2023-03-06 11:05 ` Miquel Raynal [this message]
2023-03-17 8:44 ` Tudor Ambarus
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=20230306120558.00f614fb@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=tudor.ambarus@microchip.com \
--cc=vigneshr@ti.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