From: Aidan Stewart <astewart@tektelic.com>
To: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Jiri Slaby <jirislaby@kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] serial: core: fix OF node leak
Date: Tue, 8 Jul 2025 13:37:45 +0000 [thread overview]
Message-ID: <2bd769b7f66bca4e97dba57276f5a29acdabb655.camel@tektelic.com> (raw)
In-Reply-To: <20250708085817.16070-1-johan@kernel.org>
Hi Johan,
On Tue, 2025-07-08 at 10:58 +0200, Johan Hovold wrote:
>
>
> CAUTION: This email originated from outside the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
>
>
> Make sure to drop the OF node reference taken when initialising the
> control and port devices when the devices are later released.
>
> Fixes: d36f0e9a0002 ("serial: core: restore of_node information in
> sysfs")
> Cc: Aidan Stewart <astewart@tektelic.com>
> Signed-off-by: Johan Hovold <johan@kernel.org>
> ---
> drivers/tty/serial/serial_base_bus.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/tty/serial/serial_base_bus.c
> b/drivers/tty/serial/serial_base_bus.c
> index cb3b127b06b6..22749ab0428a 100644
> --- a/drivers/tty/serial/serial_base_bus.c
> +++ b/drivers/tty/serial/serial_base_bus.c
> @@ -13,6 +13,7 @@
> #include <linux/device.h>
> #include <linux/idr.h>
> #include <linux/module.h>
> +#include <linux/of.h>
> #include <linux/serial_core.h>
> #include <linux/slab.h>
> #include <linux/spinlock.h>
> @@ -93,6 +94,7 @@ static void serial_base_ctrl_release(struct device
> *dev)
> {
> struct serial_ctrl_device *ctrl_dev =
> to_serial_base_ctrl_device(dev);
>
> + of_node_put(dev->of_node);
> kfree(ctrl_dev);
> }
>
> @@ -140,6 +142,7 @@ static void serial_base_port_release(struct device
> *dev)
> {
> struct serial_port_device *port_dev =
> to_serial_base_port_device(dev);
>
> + of_node_put(dev->of_node);
> kfree(port_dev);
> }
>
> --
> 2.49.0
Thanks for the fix. I think this also needs to go into -stable, as the
previous changes have already landed there (6.12.36 and 6.15.5).
Aidan
next prev parent reply other threads:[~2025-07-08 13:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 8:58 Johan Hovold
2025-07-08 13:37 ` Aidan Stewart [this message]
2025-07-08 15:23 ` Johan Hovold
2025-07-08 15:26 ` Greg Kroah-Hartman
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=2bd769b7f66bca4e97dba57276f5a29acdabb655.camel@tektelic.com \
--to=astewart@tektelic.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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
all inboxes | Powered by JetHome®