From: Jiri Slaby <jirislaby@kernel.org>
To: Yunhui Cui <cuiyunhui@bytedance.com>,
arnd@arndb.de, andriy.shevchenko@linux.intel.com,
benjamin.larsson@genexis.eu, gregkh@linuxfoundation.org,
heikki.krogerus@linux.intel.com, ilpo.jarvinen@linux.intel.com,
jkeeping@inmusicbrands.com, john.ogness@linutronix.de,
linux-kernel@vger.kernel.org, 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 v4 2/4] serial: 8250: introduce serial8250_discard_data()
Date: Fri, 25 Apr 2025 08:48:54 +0200 [thread overview]
Message-ID: <3a24d3ab-9567-4a0c-b904-4225ab4c489b@kernel.org> (raw)
In-Reply-To: <20250425062425.68761-2-cuiyunhui@bytedance.com>
On 25. 04. 25, 8:24, Yunhui Cui wrote:
> To prevent triggering PSLVERR, it is necessary to check whether the
> UART_LSR_DR bit of UART_LSR is set before reading UART_RX.
> Ensure atomicity of UART_LSR and UART_RX, put serial8250_discard_data()
> under port->lock.
>
> Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
> ---
> drivers/tty/serial/8250/8250.h | 15 +++++++++++
> drivers/tty/serial/8250/8250_port.c | 42 ++++++++++++++---------------
> 2 files changed, 36 insertions(+), 21 deletions(-)
>
> diff --git a/drivers/tty/serial/8250/8250.h b/drivers/tty/serial/8250/8250.h
> index b861585ca02a..5a106cf88207 100644
> --- a/drivers/tty/serial/8250/8250.h
> +++ b/drivers/tty/serial/8250/8250.h
> @@ -162,6 +162,21 @@ 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 unsigned int serial8250_discard_data(struct uart_8250_port *up)
> +{
> + u16 lsr;
Is lsr really 16-bit?
> +
> + lsr = serial_in(up, UART_LSR);
> + if (lsr & UART_LSR_DR)
> + return serial_in(up, UART_RX);
Why does a discard function return a value at all?
> +
> + return 0;
> +}
> +
> /*
> * For the 16C950
> */
> diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c
> index a913135d5217..802ac50357c0 100644
> --- a/drivers/tty/serial/8250/8250_port.c
> +++ b/drivers/tty/serial/8250/8250_port.c
...
> @@ -2137,25 +2136,21 @@ 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;
>
> serial8250_rpm_get(up);
>
> + uart_port_lock_irqsave(port, &flags);
> lsr = serial_port_in(port, UART_LSR);
> -
> - if (!(lsr & UART_LSR_DR)) {
> - status = NO_POLL_CHAR;
> - goto out;
> - }
> -
> - status = serial_port_in(port, UART_RX);
> + if ((lsr & UART_LSR_DR))
Too many parentheses.
> + status = serial_port_in(port, UART_RX);
> + uart_port_unlock_irqrestore(port, flags);
thanks,
--
js
suse labs
next prev parent reply other threads:[~2025-04-25 6:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 6:24 [PATCH v4 1/4] serial: 8250: fix panic due to PSLVERR Yunhui Cui
2025-04-25 6:24 ` [PATCH v4 2/4] serial: 8250: introduce serial8250_discard_data() Yunhui Cui
2025-04-25 6:48 ` Jiri Slaby [this message]
2025-05-06 10:38 ` [External] " yunhui cui
2025-04-25 8:22 ` John Ogness
2025-04-26 4:47 ` kernel test robot
2025-04-26 5:59 ` kernel test robot
2025-04-25 6:24 ` [PATCH v4 3/4] serial: 8250: warning on entering dw8250_force_idle unlocked Yunhui Cui
2025-04-25 6:24 ` [PATCH v4 4/4] serial: 8250_dw: fix PSLVERR on RX_TIMEOUT Yunhui Cui
2025-04-25 6:41 ` Jiri Slaby
2025-04-25 6:43 ` Jiri Slaby
2025-04-27 11:17 ` [External] " yunhui cui
2025-04-29 3:41 ` 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=3a24d3ab-9567-4a0c-b904-4225ab4c489b@kernel.org \
--to=jirislaby@kernel.org \
--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=ilpo.jarvinen@linux.intel.com \
--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