From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Yunhui Cui <cuiyunhui@bytedance.com>
Cc: arnd@arndb.de,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
benjamin.larsson@genexis.eu,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
heikki.krogerus@linux.intel.com,
Jiri Slaby <jirislaby@kernel.org>,
jkeeping@inmusicbrands.com, john.ogness@linutronix.de,
LKML <linux-kernel@vger.kernel.org>,
linux-serial <linux-serial@vger.kernel.org>,
markus.mayer@linaro.org, matt.porter@linaro.org,
namcao@linutronix.de, paulmck@kernel.org, pmladek@suse.com,
schnelle@linux.ibm.com, sunilvl@ventanamicro.com,
tim.kryger@linaro.org
Subject: Re: [PATCH v5 2/4] serial: 8250: avoid potential PSLVERR issue
Date: Tue, 6 May 2025 15:00:25 +0300 (EEST) [thread overview]
Message-ID: <6801686d-a0b3-7093-1293-cdac6ad055e4@linux.intel.com> (raw)
In-Reply-To: <20250506112321.61710-2-cuiyunhui@bytedance.com>
On Tue, 6 May 2025, Yunhui Cui wrote:
> Failure to check the UART_LSR_DR before reading UART_RX, or the
> non-atomic nature of clearing the FIFO and reading UART_RX, poses
> potential risks that could lead to PSLVERR.
Don't expect reader to know the condition how PSLVERR is triggered. I know
it's worded out in the other patch but also explain it here.
You're only explaining problem and missing what this patch does to solve
the problem.
> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
> ---
> drivers/tty/serial/8250/8250.h | 13 +++++++++
> drivers/tty/serial/8250/8250_port.c | 43 +++++++++++++++--------------
> 2 files changed, 35 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/tty/serial/8250/8250.h b/drivers/tty/serial/8250/8250.h
> index b861585ca02a..6f97ff3a197d 100644
> --- a/drivers/tty/serial/8250/8250.h
> +++ b/drivers/tty/serial/8250/8250.h
> @@ -162,6 +162,19 @@ static inline u16 serial_lsr_in(struct uart_8250_port *up)
> return lsr;
> }
>
> +/*
> + * To avoid PSLVERR, check UART_LSR_DR in UART_LSR before
> + * reading UART_RX.
> + */
> +static inline void serial8250_discard_data(struct uart_8250_port *up)
> +{
> + u16 lsr;
> +
> + lsr = serial_in(up, UART_LSR);
> + if (lsr & UART_LSR_DR)
> + serial_in(up, UART_RX);
> +}
> +
> /*
> * For the 16C950
> */
> diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c
> index a913135d5217..1666b965f6a0 100644
> --- a/drivers/tty/serial/8250/8250_port.c
> +++ b/drivers/tty/serial/8250/8250_port.c
> @@ -1357,9 +1357,8 @@ static void autoconfig_irq(struct uart_8250_port *up)
> /* Synchronize UART_IER access against the console. */
> uart_port_lock_irq(port);
> serial_out(up, UART_IER, UART_IER_ALL_INTR);
> + serial8250_discard_data(up);
> uart_port_unlock_irq(port);
> - serial_in(up, UART_LSR);
> - serial_in(up, UART_RX);
> serial_in(up, UART_IIR);
> serial_in(up, UART_MSR);
> serial_out(up, UART_TX, 0xFF);
> @@ -2137,25 +2136,22 @@ static void wait_for_xmitr(struct uart_8250_port *up, int bits)
> static int serial8250_get_poll_char(struct uart_port *port)
> {
> struct uart_8250_port *up = up_to_u8250p(port);
> - int status;
> + int status = NO_POLL_CHAR;
> u16 lsr;
> + unsigned long flags;
>
> serial8250_rpm_get(up);
>
> + uart_port_lock_irqsave(port, &flags);
> lsr = serial_port_in(port, UART_LSR);
> + if (lsr & UART_LSR_DR)
> + status = serial_port_in(port, UART_RX);
> + uart_port_unlock_irqrestore(port, flags);
>
> - if (!(lsr & UART_LSR_DR)) {
> - status = NO_POLL_CHAR;
> - goto out;
> - }
> -
> - status = serial_port_in(port, UART_RX);
> -out:
> serial8250_rpm_put(up);
> return status;
Not a problem that originates from you, but IMO calling this variable
"status" is quite misleading when it is the character (or NO_POLL_CHAR
is no character is present).
> }
>
> -
> static void serial8250_put_poll_char(struct uart_port *port,
> unsigned char c)
> {
> @@ -2264,13 +2260,17 @@ int serial8250_do_startup(struct uart_port *port)
> * Clear the FIFO buffers and disable them.
> * (they will be reenabled in set_termios())
> */
> + uart_port_lock_irqsave(port, &flags);
> serial8250_clear_fifos(up);
>
> /*
> - * Clear the interrupt registers.
> + * Read UART_RX to clear interrupts (e.g., Character Timeout).
> + * No data on UART_IIR_RX_TIMEOUT, UART_LSR_DR won't set.
> + * FIFO disabled, read UART_RX without LSR check, no PSLVERR.
I don't understand what the last two lines mean and I don't see the
connection to the code that is below the comment either, could you try to
rephrase the comment.
> */
> serial_port_in(port, UART_LSR);
> serial_port_in(port, UART_RX);
> + uart_port_unlock_irqrestore(port, flags);
> serial_port_in(port, UART_IIR);
> serial_port_in(port, UART_MSR);
>
> @@ -2429,15 +2429,14 @@ int serial8250_do_startup(struct uart_port *port)
> }
>
> dont_test_tx_en:
> - uart_port_unlock_irqrestore(port, flags);
>
> /*
> * Clear the interrupt registers again for luck, and clear the
> * saved flags to avoid getting false values from polling
> * routines or the previous session.
> */
> - serial_port_in(port, UART_LSR);
> - serial_port_in(port, UART_RX);
> + serial8250_discard_data(up);
> + uart_port_unlock_irqrestore(port, flags);
> serial_port_in(port, UART_IIR);
> serial_port_in(port, UART_MSR);
> up->lsr_saved_flags = 0;
> @@ -2519,7 +2518,6 @@ void serial8250_do_shutdown(struct uart_port *port)
> port->mctrl &= ~TIOCM_OUT2;
>
> serial8250_set_mctrl(port, port->mctrl);
> - uart_port_unlock_irqrestore(port, flags);
>
> /*
> * Disable break condition and FIFOs
> @@ -2527,6 +2525,14 @@ void serial8250_do_shutdown(struct uart_port *port)
> serial_port_out(port, UART_LCR,
> serial_port_in(port, UART_LCR) & ~UART_LCR_SBC);
> serial8250_clear_fifos(up);
> + /*
> + * Read data port to reset things, and then unlink from
> + * the IRQ chain.
> + * Since reading UART_RX clears interrupts, doing so with
> + * FIFO disabled won't trigger PSLVERR.
> + */
> + serial_port_in(port, UART_RX);
> + uart_port_unlock_irqrestore(port, flags);
>
> #ifdef CONFIG_SERIAL_8250_RSA
> /*
> @@ -2535,11 +2541,6 @@ void serial8250_do_shutdown(struct uart_port *port)
> disable_rsa(up);
> #endif
>
> - /*
> - * Read data port to reset things, and then unlink from
> - * the IRQ chain.
> - */
> - serial_port_in(port, UART_RX);
> serial8250_rpm_put(up);
>
> up->ops->release_irq(up);
>
--
i.
next prev parent reply other threads:[~2025-05-06 12:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 11:23 [PATCH v5 1/4] serial: 8250: fix panic due to PSLVERR Yunhui Cui
2025-05-06 11:23 ` [PATCH v5 2/4] serial: 8250: avoid potential PSLVERR issue Yunhui Cui
2025-05-06 12:00 ` Ilpo Järvinen [this message]
2025-05-12 6:37 ` [External] " yunhui cui
2025-05-12 10:27 ` Ilpo Järvinen
2025-05-12 11:46 ` yunhui cui
2025-05-12 12:02 ` Ilpo Järvinen
2025-05-12 14:00 ` yunhui cui
2025-05-06 11:23 ` [PATCH v5 3/4] serial: 8250_dw: warning on entering dw8250_force_idle unlocked Yunhui Cui
2025-05-06 12:06 ` Ilpo Järvinen
2025-05-06 12:08 ` Ilpo Järvinen
2025-05-06 11:23 ` [PATCH v5 4/4] serial: 8250_dw: fix PSLVERR on RX_TIMEOUT Yunhui Cui
2025-05-06 12:25 ` Ilpo Järvinen
2025-05-08 11:51 ` [External] " yunhui cui
2025-05-06 12:34 ` [PATCH v5 1/4] serial: 8250: fix panic due to PSLVERR Ilpo Järvinen
2025-05-12 3:06 ` [External] " yunhui cui
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=6801686d-a0b3-7093-1293-cdac6ad055e4@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=benjamin.larsson@genexis.eu \
--cc=cuiyunhui@bytedance.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=jkeeping@inmusicbrands.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=markus.mayer@linaro.org \
--cc=matt.porter@linaro.org \
--cc=namcao@linutronix.de \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=schnelle@linux.ibm.com \
--cc=sunilvl@ventanamicro.com \
--cc=tim.kryger@linaro.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