From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Jason Wessel <jason.wessel@windriver.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
Douglas Anderson <dianders@chromium.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
kgdb-bugreport@lists.sourceforge.net,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] tty: serial: kgdboc: fix mutex locking order for configure_kgdboc()
Date: Thu, 12 Jan 2023 16:40:16 +0100 [thread overview]
Message-ID: <Y8Ap4B75PNy5/lHo@alley> (raw)
In-Reply-To: <Y77imoYMaZZZz28x@alley>
On Wed 2023-01-11 17:23:55, Petr Mladek wrote:
> On Wed 2023-01-11 15:57:10, John Ogness wrote:
> > Several mutexes are taken while setting up console serial ports. In
> > particular, the tty_port->mutex and @console_mutex are taken:
> >
> > serial_pnp_probe
> > serial8250_register_8250_port
> > uart_add_one_port (locks tty_port->mutex)
> > uart_configure_port
> > register_console (locks @console_mutex)
> >
> > In order to synchronize kgdb's tty_find_polling_driver() with
> > register_console(), commit 6193bc90849a ("tty: serial: kgdboc:
> > synchronize tty_find_polling_driver() and register_console()") takes
> > the @console_mutex. However, this leads to the following call chain
> > (with locking):
> >
> > platform_probe
> > kgdboc_probe
> > configure_kgdboc (locks @console_mutex)
> > tty_find_polling_driver
> > uart_poll_init (locks tty_port->mutex)
> > uart_set_options
> >
> > This is clearly deadlock potential due to the reverse lock ordering.
>
> Great catch!
>
> > Since uart_set_options() requires holding @console_mutex in order to
> > serialize early initialization of the serial-console lock, take the
> > @console_mutex in uart_poll_init() instead of configure_kgdboc().
> >
> > Since configure_kgdboc() was using @console_mutex for safe traversal
> > of the console list, change it to use the SRCU iterator instead.
> >
> > Add comments to uart_set_options() kerneldoc mentioning that it
> > requires holding @console_mutex (aka the console_list_lock).
> >
> > Fixes: 6193bc90849a ("tty: serial: kgdboc: synchronize tty_find_polling_driver() and register_console()")
> > Signed-off-by: John Ogness <john.ogness@linutronix.de>
>
> > --- a/drivers/tty/serial/kgdboc.c
> > +++ b/drivers/tty/serial/kgdboc.c
> > @@ -189,15 +190,6 @@ static int configure_kgdboc(void)
> > if (kgdboc_register_kbd(&cptr))
> > goto do_register;
> >
> > - /*
> > - * tty_find_polling_driver() can call uart_set_options()
> > - * (via poll_init) to configure the uart. Take the console_list_lock
> > - * in order to synchronize against register_console(), which can also
> > - * configure the uart via uart_set_options(). This also allows safe
> > - * traversal of the console list.
> > - */
> > - console_list_lock();
> > -
> > p = tty_find_polling_driver(cptr, &tty_line);
> > if (!p) {
> > console_list_unlock();
>
> This console_list_unlock() should be removed here as well.
This seems to be the only problem. Otherwise, the patch looks good to
me.
After removing the superfluous console_list_unlock():
Reviewed-by: Petr Mladek <pmladek@suse.com>
John, would you mind to send v2, please?
Best Regards,
Petr
next prev parent reply other threads:[~2023-01-12 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 14:51 [PATCH] tty: serial: kgdboc: fix mutex locking order for configure_kgdboc() John Ogness
2023-01-11 16:23 ` Petr Mladek
2023-01-12 15:40 ` Petr Mladek [this message]
2023-01-13 2:32 ` Sergey Senozhatsky
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=Y8Ap4B75PNy5/lHo@alley \
--to=pmladek@suse.com \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=jason.wessel@windriver.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tglx@linutronix.de \
/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