From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Myeonghun Pak <mhun512@gmail.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
Dmitry Rokosov <ddrokosov@sberdevices.ru>,
linux-serial@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Ijae Kim <ae878000@gmail.com>
Subject: Re: [PATCH] tty: serial: meson: fix UART driver lifetime
Date: Wed, 23 Sep 2026 12:15:38 +0200 [thread overview]
Message-ID: <2026092344-unlawful-hurling-c87e@gregkh> (raw)
In-Reply-To: <20260913034148.15068-1-mhun512@gmail.com>
On Sat, Sep 12, 2026 at 11:41:48PM -0400, Myeonghun Pak wrote:
> Moving Amlogic UART registration into probe left the first driver
> registration behind if uart_add_one_port() failed. Adding the separate
> ttyS driver later also exposed a global last-port test: removing the last
> port of one driver kept it registered whenever the other had a port.
>
> Track whether probe registered the driver and undo it when port addition
> fails. On remove, retain the current driver only if a remaining port maps
> to that driver. Serialize the shared lifecycle decisions against parallel
> probe and remove operations.
>
> This issue was identified during our ongoing static-analysis research while
> reviewing kernel code.
>
> Fixes: bcb5645f99ef ("tty: serial: meson: redesign the module to platform_driver")
> Fixes: e71aab9d6132 ("tty: serial: meson: apply ttyS devname instead of ttyAML for new SoCs")
> Cc: stable@vger.kernel.org
> Assisted-by: OpenAI:GPT-5.6
> Co-developed-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
> ---
> drivers/tty/serial/meson_uart.c | 52 +++++++++++++++++++++++++--------
> 1 file changed, 40 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/tty/serial/meson_uart.c b/drivers/tty/serial/meson_uart.c
> index a6cb2a535..4bd9d9826 100644
> --- a/drivers/tty/serial/meson_uart.c
> +++ b/drivers/tty/serial/meson_uart.c
> @@ -12,6 +12,7 @@
> #include <linux/io.h>
> #include <linux/iopoll.h>
> #include <linux/module.h>
> +#include <linux/mutex.h>
> #include <linux/kernel.h>
> #include <linux/of.h>
> #include <linux/platform_device.h>
> @@ -80,6 +81,7 @@ static struct uart_driver meson_uart_driver_ttyAML;
> static struct uart_driver meson_uart_driver_ttyS;
>
> static struct uart_port *meson_ports[AML_UART_PORT_NUM];
> +static DEFINE_MUTEX(meson_uart_mutex);
>
> struct meson_uart_data {
> struct uart_driver *uart_driver;
> @@ -692,6 +694,16 @@ static struct uart_driver *meson_uart_current(const struct meson_uart_data *pd)
> pd->uart_driver : &meson_uart_driver_ttyAML;
> }
>
> +static bool meson_uart_has_ports(struct uart_driver *uart_driver)
As you require a lock to be held here, document it properly so the
compiler will catch it when you get it wrong.
> +{
> + for (int id = 0; id < AML_UART_PORT_NUM; id++)
> + if (meson_ports[id] &&
> + meson_uart_current(meson_ports[id]->private_data) == uart_driver)
> + return true;
> +
> + return false;
> +}
> +
> static int meson_uart_probe(struct platform_device *pdev)
> {
> const struct meson_uart_data *priv_data;
> @@ -702,6 +714,7 @@ static int meson_uart_probe(struct platform_device *pdev)
> int ret = 0;
> int irq;
> bool has_rtscts;
> + bool registered = false;
>
> if (pdev->dev.of_node)
> pdev->id = of_alias_get_id(pdev->dev.of_node, "serial");
> @@ -731,11 +744,6 @@ static int meson_uart_probe(struct platform_device *pdev)
> of_property_read_u32(pdev->dev.of_node, "fifo-size", &fifosize);
> has_rtscts = of_property_read_bool(pdev->dev.of_node, "uart-has-rtscts");
>
> - if (meson_ports[pdev->id]) {
> - return dev_err_probe(&pdev->dev, -EBUSY,
> - "port %d already allocated\n", pdev->id);
> - }
> -
> port = devm_kzalloc(&pdev->dev, sizeof(struct uart_port), GFP_KERNEL);
> if (!port)
> return -ENOMEM;
> @@ -748,11 +756,22 @@ static int meson_uart_probe(struct platform_device *pdev)
>
> uart_driver = meson_uart_current(priv_data);
>
> + mutex_lock(&meson_uart_mutex);
guard?
thanks,
greg k-h
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
prev parent reply other threads:[~2026-09-23 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-13 3:41 Myeonghun Pak
2026-09-13 3:52 ` sashiko-bot
2026-09-23 10:15 ` Greg Kroah-Hartman [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=2026092344-unlawful-hurling-c87e@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=ae878000@gmail.com \
--cc=ddrokosov@sberdevices.ru \
--cc=jbrunet@baylibre.com \
--cc=jirislaby@kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=mhun512@gmail.com \
--cc=neil.armstrong@linaro.org \
--cc=stable@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®