From: Greg KH <gregkh@linuxfoundation.org>
To: yunhui cui <cuiyunhui@bytedance.com>
Cc: John Ogness <john.ogness@linutronix.de>,
arnd@arndb.de, andriy.shevchenko@linux.intel.com,
benjamin.larsson@genexis.eu, heikki.krogerus@linux.intel.com,
ilpo.jarvinen@linux.intel.com, jirislaby@kernel.org,
jkeeping@inmusicbrands.com, 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,
stable@vger.kernel.org
Subject: Re: [External] Re: [PATCH v9 1/4] serial: 8250: fix panic due to PSLVERR
Date: Thu, 17 Jul 2025 14:32:54 +0200 [thread overview]
Message-ID: <2025071729-exemplary-smelting-08fe@gregkh> (raw)
In-Reply-To: <CAEEQ3wnBJUjArdfs+vgrsfoQaVJPKD3uwD8hwgg963fUBaNGrA@mail.gmail.com>
On Thu, Jul 17, 2025 at 08:19:48PM +0800, yunhui cui wrote:
> Hi John,
>
> On Fri, Jun 20, 2025 at 7:20 PM John Ogness <john.ogness@linutronix.de> wrote:
> >
> > On 2025-06-10, Yunhui Cui <cuiyunhui@bytedance.com> wrote:
> > > When the PSLVERR_RESP_EN parameter is set to 1, the device generates
> > > an error response if an attempt is made to read an empty RBR (Receive
> > > Buffer Register) while the FIFO is enabled.
> > >
> > > In serial8250_do_startup(), calling serial_port_out(port, UART_LCR,
> > > UART_LCR_WLEN8) triggers dw8250_check_lcr(), which invokes
> > > dw8250_force_idle() and serial8250_clear_and_reinit_fifos(). The latter
> > > function enables the FIFO via serial_out(p, UART_FCR, p->fcr).
> > > Execution proceeds to the serial_port_in(port, UART_RX).
> > > This satisfies the PSLVERR trigger condition.
> > >
> > > When another CPU (e.g., using printk()) is accessing the UART (UART
> > > is busy), the current CPU fails the check (value & ~UART_LCR_SPAR) ==
> > > (lcr & ~UART_LCR_SPAR) in dw8250_check_lcr(), causing it to enter
> > > dw8250_force_idle().
> > >
> > > Put serial_port_out(port, UART_LCR, UART_LCR_WLEN8) under the port->lock
> > > to fix this issue.
> > >
> > > Panic backtrace:
> > > [ 0.442336] Oops - unknown exception [#1]
> > > [ 0.442343] epc : dw8250_serial_in32+0x1e/0x4a
> > > [ 0.442351] ra : serial8250_do_startup+0x2c8/0x88e
> > > ...
> > > [ 0.442416] console_on_rootfs+0x26/0x70
> > >
> > > Fixes: c49436b657d0 ("serial: 8250_dw: Improve unwritable LCR workaround")
> > > Link: https://lore.kernel.org/all/84cydt5peu.fsf@jogness.linutronix.de/T/
> > > Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
> > > Cc: stable@vger.kernel.org
> >
> > Reviewed-by: John Ogness <john.ogness@linutronix.de>
>
> In this patchset, patch[4] has been dropped, and patch[2] may still
> need discussion. Could you please pick patch[1] and patch[3] first?
Please resend just the patches you want applied, picking out of a series
is hard with our current tools, and confusing.
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-17 12:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 9:21 [PATCH v9 0/4] Serial: 8250: Fix PSLVERR related issues Yunhui Cui
2025-06-10 9:21 ` [PATCH v9 1/4] serial: 8250: fix panic due to PSLVERR Yunhui Cui
2025-06-20 11:19 ` John Ogness
2025-07-17 12:19 ` [External] " yunhui cui
2025-07-17 12:32 ` Greg KH [this message]
2025-06-10 9:21 ` [PATCH v9 2/4] serial: 8250_dw: fix PSLVERR on RX_TIMEOUT Yunhui Cui
2025-06-23 6:50 ` yunhui cui
2025-06-23 8:32 ` John Ogness
2025-07-11 2:19 ` [External] " yunhui cui
2025-07-17 14:14 ` John Ogness
2025-07-18 15:20 ` Doug Anderson
2025-06-10 9:21 ` [PATCH v9 3/4] serial: 8250: avoid potential PSLVERR issue Yunhui Cui
2025-06-20 11:20 ` John Ogness
2025-06-10 9:21 ` [PATCH v9 4/4] serial: 8250_dw: assert port->lock is held in dw8250_force_idle() Yunhui Cui
2025-06-20 12:14 ` John Ogness
2025-06-23 6:44 ` [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=2025071729-exemplary-smelting-08fe@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=benjamin.larsson@genexis.eu \
--cc=cuiyunhui@bytedance.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=ilpo.jarvinen@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=stable@vger.kernel.org \
--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