From: Jiri Slaby <jirislaby@kernel.org>
To: Fan Wu <fanwu01@zju.edu.cn>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
stable@vger.kernel.org
Subject: Re: [PATCH] serial: imx: cancel RS485 trigger hrtimers in shutdown and remove
Date: Wed, 19 Aug 2026 06:26:28 +0200 [thread overview]
Message-ID: <46936686-3bdd-4d36-9124-e8d3376ad5ea@kernel.org> (raw)
In-Reply-To: <20260819021916.442827-1-fanwu01@zju.edu.cn>
On 19. 08. 26, 4:19, Fan Wu wrote:
> The rs485 delay hrtimers trigger_start_tx and trigger_stop_tx are
> embedded in the devm allocated struct imx_port, and their callbacks
> reach the port through container_of() and touch registers under the
> port lock. Nothing cancels them synchronously: the tx paths only
> call hrtimer_try_to_cancel(), which does not wait for a running
> callback, and the bounded wait in imx_uart_shutdown() can give up,
> force tx_state to OFF, and leave a timer armed. After
> imx_uart_remove() returns, devm frees the port and a late callback
> dereferences freed memory.
>
> Cancel both timers at the end of imx_uart_shutdown(), after the port
> lock is dropped and before the clocks are disabled, and again in
> imx_uart_remove() before the devm free:
> serial core does not call the
> driver shutdown on every path that reaches remove().
Could you be more specific on what path it does not?
thanks,
--
js
suse labs
next prev parent reply other threads:[~2026-08-19 4:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 2:19 [PATCH] serial: imx: cancel RS485 trigger hrtimers in shutdown and remove Fan Wu
2026-08-19 2:35 ` sashiko-bot
2026-08-19 4:26 ` Jiri Slaby [this message]
2026-08-19 6:39 ` Fan Wu
2026-10-01 8:57 ` Greg Kroah-Hartman
2026-09-23 10:17 ` Greg Kroah-Hartman
2026-09-27 14:35 ` Fan Wu
2026-09-27 16:28 ` Greg Kroah-Hartman
2026-09-28 1:21 ` Fan Wu
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=46936686-3bdd-4d36-9124-e8d3376ad5ea@kernel.org \
--to=jirislaby@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=fanwu01@zju.edu.cn \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.