From: Boris Brezillon <boris.brezillon@collabora.com>
To: "Dr. David Alan Gilbert" <linux@treblig.org>
Cc: nicolas.ferre@microchip.com, miquel.raynal@bootlin.com,
richard@nod.at, linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: of atmel_pmecc_destroy_user
Date: Mon, 30 Sep 2024 09:08:17 +0200 [thread overview]
Message-ID: <20240930090817.0a86e538@collabora.com> (raw)
In-Reply-To: <ZvmIvRJCf6VhHvpo@gallifrey>
Hi David,
On Sun, 29 Sep 2024 17:05:01 +0000
"Dr. David Alan Gilbert" <linux@treblig.org> wrote:
> Hi Boris and co,
> One of my scripts noticed that 'atmel_pmecc_destroy_user'
> isn't called anywhere; I was going to delete it, but hmm, I wonder
> if it's actually a missing call and leaking (in the unlikely case
> the device was ever removed).
>
> It was added by your:
> commit f88fc122cc34c2545dec9562eaab121494e401ef
> Author: Boris Brezillon <bbrezillon@kernel.org>
> Date: Thu Mar 16 09:02:40 2017 +0100
>
> mtd: nand: Cleanup/rework the atmel_nand driver
>
> and I see the allocation in:
> user = kzalloc(size, GFP_KERNEL);
> in
> nand->pmecc = atmel_pmecc_create_user(nc->pmecc, &req);
> called in atmel_nand_pmecc_init
> from atmel_nand_ecc_init
> from atmel_hsmc_nand_ecc_init
>
> But I don't see any freeing.
>
> (I don't knowingly have hardware to test a fix, although I guess
> there's probably one somewhere....)
>
> Suggestions?
There's definitely a leak. I haven't looked at NAND stuff for a while
though, so I'll let Miquel advise you on where
atmel_pmecc_destroy_user() should be called.
Regards,
Boris
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-09-30 7:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 17:05 of atmel_pmecc_destroy_user Dr. David Alan Gilbert
2024-09-30 7:08 ` Boris Brezillon [this message]
2024-10-01 20:37 ` Dr. David Alan Gilbert
2024-10-01 20:41 ` Miquel Raynal
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=20240930090817.0a86e538@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@treblig.org \
--cc=miquel.raynal@bootlin.com \
--cc=nicolas.ferre@microchip.com \
--cc=richard@nod.at \
/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