From: Johan Hovold <johan@kernel.org>
To: Tapio Reijonen <tapio.reijonen@vaisala.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v2 2/2] serial: core: do not touch the port after dropping the last reference
Date: Thu, 12 Nov 2026 15:32:34 +0100 [thread overview]
Message-ID: <avXOArIk9Cep-rCI@hovoldconsulting.com> (raw)
In-Reply-To: <20261112-serial-core-remove-deadlock-v2-2-d3ee4ccec37a@vaisala.com>
On Thu, Nov 12, 2026 at 04:37:28AM +0000, Tapio Reijonen wrote:
> uart_port_deref() decrements the reference count through uport->state
> and then reads uport->state again for the wake_up(). The last
> decrement is what lets serial_core_remove_one_port() return, and the
> driver may free its struct uart_port right after that. A reference
> holder that drops the last reference can therefore read the freed port
> on its way to the wake_up().
>
> Read the state pointer once, before the decrement. The uart_state
> belongs to the uart_driver and lives until uart_unregister_driver(),
> so the wake_up() target outlives the port. Drivers that unregister the
> uart_driver in the same remove() are a separate matter and not changed
> here.
>
> Found by review of the removal path while fixing the deadlock between
> port removal and a blocked tcdrain(); not reproduced.
>
> Fixes: 9ed19428a51d ("serial: core: Prevent unsafe uart port access, part 2")
> Cc: stable@vger.kernel.org
> Reviewed-by: Johan Hovold <johan@kernel.org>
> Signed-off-by: Tapio Reijonen <tapio.reijonen@vaisala.com>
> static inline void uart_port_deref(struct uart_port *uport)
> {
> - if (atomic_dec_and_test(&uport->state->refcount))
> - wake_up(&uport->state->remove_wait);
> + struct uart_state *state = uport->state;
Hmm. Don't we also need a READ_ONCE() here to prevent the compiler from
doing something silly?
> +
> + if (atomic_dec_and_test(&state->refcount))
> + wake_up(&state->remove_wait);
> }
Johan
prev parent reply other threads:[~2026-11-12 14:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 4:37 [PATCH v2 0/2] serial: core: two fixes for the port removal path Tapio Reijonen
2026-11-12 4:37 ` [PATCH v2 1/2] serial: core: do not hold the port mutex while waiting for references Tapio Reijonen
2026-11-12 4:52 ` sashiko-bot
2026-11-12 4:37 ` [PATCH v2 2/2] serial: core: do not touch the port after dropping the last reference Tapio Reijonen
2026-11-12 4:41 ` sashiko-bot
2026-11-12 14:32 ` Johan Hovold [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=avXOArIk9Cep-rCI@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tapio.reijonen@vaisala.com \
/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