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 3/4] serial: 8250_dw: warning on entering dw8250_force_idle unlocked
Date: Tue, 6 May 2025 15:08:46 +0300 (EEST) [thread overview]
Message-ID: <f4fe790b-8dcd-1002-f6cd-0fbf451d28e1@linux.intel.com> (raw)
In-Reply-To: <71a295db-72ea-bf2a-338f-416b178f5305@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1837 bytes --]
Also, you should also improve the shortlog (in Subject) to something less
vague, e.g.:
serial: 8250_dw: assert port->lock is held in dw8250_force_idle()
On Tue, 6 May 2025, Ilpo Järvinen wrote:
> On Tue, 6 May 2025, Yunhui Cui wrote:
>
> > Read UART_RX and check UART_LSR_DR in critical section. Unsure if
>
> Unsure if -> Ensure the
>
> > caller of dw8250_force_idle() holds port->lock. Don't acquire it
> > directly to avoid deadlock. Use lockdep_assert_held_once for warning.
>
> Add (), although the last two sentences don't seem that useful, IMO.
>
> >
> > Signed-off-by: Yunhui Cui <cuiyunhui@bytedance.com>
> > ---
> > drivers/tty/serial/8250/8250_dw.c | 8 ++++++++
> > 1 file changed, 8 insertions(+)
> >
> > diff --git a/drivers/tty/serial/8250/8250_dw.c b/drivers/tty/serial/8250/8250_dw.c
> > index af24ec25d976..f41c4a9ed58b 100644
> > --- a/drivers/tty/serial/8250/8250_dw.c
> > +++ b/drivers/tty/serial/8250/8250_dw.c
> > @@ -13,6 +13,7 @@
> > #include <linux/delay.h>
> > #include <linux/device.h>
> > #include <linux/io.h>
> > +#include <linux/lockdep.h>
> > #include <linux/mod_devicetable.h>
> > #include <linux/module.h>
> > #include <linux/notifier.h>
> > @@ -112,6 +113,13 @@ static void dw8250_force_idle(struct uart_port *p)
> > struct uart_8250_port *up = up_to_u8250p(p);
> > unsigned int lsr;
> >
> > + /*
> > + * The serial_in(p, UART_RX) should be under port->lock, but we can't add
> > + * it to avoid AA deadlock as we're unsure if serial_out*(...UART_LCR)
> > + * is under port->lock.
>
> I'm left to wonder who/what "we" is here? Could you change it something
> more precise.
>
> > + */
> > + lockdep_assert_held_once(&p->lock);
> > +
> > serial8250_clear_and_reinit_fifos(up);
> >
> > /*
> >
>
>
--
i.
next prev parent reply other threads:[~2025-05-06 12:08 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
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 [this message]
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=f4fe790b-8dcd-1002-f6cd-0fbf451d28e1@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