From: Conor Dooley <conor@kernel.org>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: conor.dooley@microchip.com, daire.mcnamara@microchip.com,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
stable@vger.kernel.org
Subject: Re: [PATCH] soc: microchip: mpfs: Fix flash leak in mpfs_sys_controller_probe()
Date: Thu, 8 Oct 2026 14:18:11 +0100 [thread overview]
Message-ID: <20261008-47741881fb032091ea3d7f0c@squawk> (raw)
In-Reply-To: <20261002-garnish-president-6e8abfdacf4c@spud>
[-- Attachment #1: Type: text/plain, Size: 3203 bytes --]
On Fri, Oct 02, 2026 at 06:48:28PM +0100, Conor Dooley wrote:
> On Thu, Sep 17, 2026 at 03:35:50PM +0000, Wentao Liang wrote:
> > of_get_mtd_device_by_node() returns an MTD device reference that the
> > caller has to drop with put_mtd_device(). The probe error paths return
> > without releasing it, and the reference stored in sys_controller->flash
> > is never dropped when the controller is destroyed either.
> >
> > Release the flash on the probe error paths and in
> > mpfs_sys_controller_delete(), so the reference is always put.
>
> Is this diff sufficient?
> If probe passes, shouldn't the driver also call this during removal?
>
> Removal here just decrements the refcount, so the delete function is
> where the call would have to go. Another patch for this driver pointed
> out that the teardown code should actually call mpfs_sys_controller_put()
> https://patchwork.kernel.org/project/lei-conor/patch/20260924110054.1553880-1-lgs201920130244@gmail.com/
> so the right thing to do here is probably a mix of what you've got here
> and what was done in that patch?
>
> I note that the other user of this function, u-boot-env.c, doesn't call
> this either.
I've applied a v2 of that patch I mentioned, so I'll expect a new
iteration here on top of that:
https://patchwork.kernel.org/project/lei-conor/patch/20261007121743.192486-1-lgs201920130244@gmail.com/
Cheers,
Conor.
>
> Cheers,
> Conor.
>
> >
> > Fixes: 742aa6c563d2 ("soc: microchip: mpfs: enable access to the system controller's flash")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> > ---
> > drivers/soc/microchip/mpfs-sys-controller.c | 9 ++++++++-
> > 1 file changed, 8 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/soc/microchip/mpfs-sys-controller.c b/drivers/soc/microchip/mpfs-sys-controller.c
> > index 92d1142a59e6..ad57b09e5807 100644
> > --- a/drivers/soc/microchip/mpfs-sys-controller.c
> > +++ b/drivers/soc/microchip/mpfs-sys-controller.c
> > @@ -98,6 +98,8 @@ static void mpfs_sys_controller_delete(struct kref *kref)
> > struct mpfs_sys_controller *sys_controller =
> > container_of(kref, struct mpfs_sys_controller, consumers);
> >
> > + if (sys_controller->flash)
> > + put_mtd_device(sys_controller->flash);
> > mbox_free_channel(sys_controller->chan);
> > kfree(sys_controller);
> > }
> > @@ -159,7 +161,8 @@ static int mpfs_sys_controller_probe(struct platform_device *pdev)
> > of_data = (struct mpfs_syscon_config *) device_get_match_data(dev);
> > if (!of_data) {
> > dev_err(dev, "Error getting match data\n");
> > - return -EINVAL;
> > + ret = -EINVAL;
> > + goto out_free;
> > }
> >
> > for (i = 0; i < of_data->nb_subdevs; i++) {
> > @@ -174,6 +177,10 @@ static int mpfs_sys_controller_probe(struct platform_device *pdev)
> > return 0;
> >
> > out_free:
> > + if (!IS_ERR_OR_NULL(sys_controller->flash))
> > + put_mtd_device(sys_controller->flash);
> > + if (!IS_ERR_OR_NULL(sys_controller->chan))
> > + mbox_free_channel(sys_controller->chan);
> > kfree(sys_controller);
> > return ret;
> > }
> > --
> > 2.34.1
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-10-08 13:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 15:35 Wentao Liang
2026-10-02 17:48 ` Conor Dooley
2026-10-08 13:18 ` Conor Dooley [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=20261008-47741881fb032091ea3d7f0c@squawk \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=stable@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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®