public inbox for linux-serial@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Yunhui Cui <cuiyunhui@bytedance.com>,
	gregkh@linuxfoundation.org, jirislaby@kernel.org,
	pmladek@suse.com, arnd@arndb.de, namcao@linutronix.de,
	benjamin.larsson@genexis.eu, schnelle@linux.ibm.com,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH] serial: 8250: fix panic due to PSLVERR
Date: Thu, 3 Apr 2025 15:10:42 +0300	[thread overview]
Message-ID: <Z-56wshiZz_1wU__@smile.fi.intel.com> (raw)
In-Reply-To: <84iknl5uex.fsf@jogness.linutronix.de>

On Thu, Apr 03, 2025 at 02:03:58PM +0206, John Ogness wrote:
> On 2025-04-03, 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 dont_test_tx_en label:
> > ...
> > serial_port_in(port, UART_RX);
> > This satisfies the PSLVERR trigger condition.
> >
> > Because 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), causing it to enter dw8250_force_idle().
> 
> Didn't this[0] patch resolve this exact issue?

I see it applied (in v6.0), but version in the traceback seems from v6.12.
I think this is about race condition so only locking parts should suffice.

> [0] https://lore.kernel.org/lkml/20220713131722.2316829-1-vamshigajjela@google.com

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2025-04-03 12:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03  9:03 [PATCH] serial: 8250: fix panic due to PSLVERR Yunhui Cui
2025-04-03 11:36 ` Andy Shevchenko
2025-04-03 11:50   ` Andy Shevchenko
2025-04-04  2:31     ` [External] " yunhui cui
2025-04-04 10:21       ` Andy Shevchenko
2025-04-07 13:00         ` yunhui cui
2025-04-07 14:34           ` Andy Shevchenko
2025-04-04  2:44   ` yunhui cui
2025-04-04 10:58     ` Andy Shevchenko
2025-04-07 13:22       ` yunhui cui
2025-04-07 14:37         ` Andy Shevchenko
2025-04-03 11:57 ` John Ogness
2025-04-03 12:10   ` Andy Shevchenko [this message]
2025-04-03 12:49   ` [External] " yunhui cui
2025-04-03 13:46     ` John Ogness
2025-04-03 14:14       ` 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=Z-56wshiZz_1wU__@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=benjamin.larsson@genexis.eu \
    --cc=cuiyunhui@bytedance.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=namcao@linutronix.de \
    --cc=pmladek@suse.com \
    --cc=schnelle@linux.ibm.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