From: sashiko-bot@kernel.org
To: "Phil Rosenthal" <phil@phil.gs>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] serial: core: Shut down a running console port before removing it
Date: Tue, 13 Oct 2026 14:16:53 +0000 [thread overview]
Message-ID: <sashiko-outbox-169894@kernel.org> (raw)
In-Reply-To: <20261013-serial-console-remove-v2-1-2eca1a92c10d@phil.gs>
> From: Phil Rosenthal <phil@phil.gs>
>
> A console port is not shut down when its last user closes it:
> tty_port_shutdown() returns early when tty_port::console is set, so the
> port stays initialized. For an 8250 port this leaves its interrupt
> requested or, for a port without an interrupt, its poll timer armed.
>
> serial_core_remove_one_port() relies on tty_port_tty_vhangup() to shut
> the port down before releasing its resources, but the hangup reaches
> uart_hangup() -> uart_shutdown() only when a tty is attached. For a
> console that was opened and closed, for example a serial console whose
> getty has been stopped, nothing shuts the port down. The console is
> unregistered, ->release_port() releases the registers and the core frees
> uport->name while the port is still running. On tty-next with 8250
> ports:
> [ ... ]
>
> Fixes: 761ed4a94582 ("tty: serial_core: convert uart_close to use tty_port_close")
> Cc: stable@vger.kernel.org # 6.6.x
> Assisted-by: LLM sparse
> Signed-off-by: Phil Rosenthal <phil@phil.gs>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261013-serial-console-remove-v2-1-2eca1a92c10d@phil.gs?part=1
next prev parent reply other threads:[~2026-10-13 14:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 14:07 [PATCH v2] serial: core: Shut down a running console port before removing it Phil Rosenthal via B4 Relay
2026-10-13 14:07 ` Phil Rosenthal
2026-10-13 14:16 ` sashiko-bot [this message]
2026-10-13 16:12 ` Greg Kroah-Hartman
2026-10-13 16:42 ` Phil Rosenthal
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=sashiko-outbox-169894@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=phil@phil.gs \
--cc=sashiko-reviews@lists.linux.dev \
/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.