From: Marc Zyngier <maz@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-serial@vger.kernel.org,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Guenter Roeck <linux@roeck-us.net>,
Anatoly Pugachev <matorola@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH v2] serial: core: Initialise spin lock before use in uart_configure_port()
Date: Mon, 06 Jul 2020 17:36:56 +0100 [thread overview]
Message-ID: <bfa0f8b35fe5b1864338376fa34b0db1@kernel.org> (raw)
In-Reply-To: <20200706143548.63985-1-andriy.shevchenko@linux.intel.com>
On 2020-07-06 15:35, Andy Shevchenko wrote:
> The comment near to uart_port_spin_lock_init() says:
>
> Ensure that the serial console lock is initialised early.
> If this port is a console, then the spinlock is already initialised.
>
> and there is nothing about enabled or disabled consoles. The commit
> a3cb39d258ef ("serial: core: Allow detach and attach serial device
> for console") made a change, which follows the comment, and also to
> prevent reinitialisation of the lock in use, when user detaches and
> attaches back the same console device. But this change discovers
> another issue, that uart_add_one_port() tries to access a spin lock
> that now may be uninitialised. This happens when a driver expects
> the serial core to register a console on its behalf. In this case
> we must initialise a spin lock before use.
>
> Fixes: a3cb39d258ef ("serial: core: Allow detach and attach serial
> device for console")
> Reported-by: Marc Zyngier <maz@kernel.org>
> Reported-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
> Reported-by: Guenter Roeck <linux@roeck-us.net>
> Reported-by: Anatoly Pugachev <matorola@gmail.com>
> Cc: Tony Lindgren <tony@atomide.com>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
> v2: my bad to send the version with one typo, now squashed and resent
>
> I hope this is now properly root caused. To the people in Reported-by
> list, can
> you revert the corresponding change you either reported or submitted to
> the
> certain serial driver and apply this patch and retest?
>
> Tony, can you also test that this doesn't change anything for the PM
> case for
> OMAP?
>
> Geert, I tried to explain above why the change had been made in the
> first place.
>
> drivers/tty/serial/serial_core.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serial/serial_core.c
> b/drivers/tty/serial/serial_core.c
> index 3cc183acf7ba..55f9615f0b50 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -1915,6 +1915,12 @@ static inline bool uart_console_enabled(struct
> uart_port *port)
> return uart_console(port) && (port->cons->flags & CON_ENABLED);
> }
>
> +static inline void uart_any_port_spin_lock_init(struct uart_port
> *port)
nit: __uart_port_spin_lock_init() looks like a better name to me
(as a primitive of uart_port_spin_lock_init). You can also drop
the inline which doesn't mean much these days (and this isn't
a hot path).
> +{
> + spin_lock_init(&port->lock);
> + lockdep_set_class(&port->lock, &port_lock_key);
> +}
> +
> /*
> * Ensure that the serial console lock is initialised early.
> * If this port is a console, then the spinlock is already
> initialised.
> @@ -1924,8 +1930,7 @@ static inline void
> uart_port_spin_lock_init(struct uart_port *port)
> if (uart_console(port))
> return;
>
> - spin_lock_init(&port->lock);
> - lockdep_set_class(&port->lock, &port_lock_key);
> + uart_any_port_spin_lock_init(port);
> }
>
> #if defined(CONFIG_SERIAL_CORE_CONSOLE) ||
> defined(CONFIG_CONSOLE_POLL)
> @@ -2371,6 +2376,13 @@ uart_configure_port(struct uart_driver *drv,
> struct uart_state *state,
> /* Power up port for set_mctrl() */
> uart_change_pm(state, UART_PM_STATE_ON);
>
> + /*
> + * If this driver supports console, and it hasn't been
> + * successfully registered yet, initialise spin lock for it.
> + */
> + if (port->cons && !(port->cons->flags & CON_ENABLED))
> + uart_any_port_spin_lock_init(port);
> +
> /*
> * Ensure that the modem control lines are de-activated.
> * keep the DTR setting that is set in uart_set_options()
Otherwise looks OK to me (having tested an earlier version).
With the above addressed:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-07-06 16:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 14:35 [PATCH v2] serial: core: Initialise spin lock before use in uart_configure_port() Andy Shevchenko
2020-07-06 16:36 ` Marc Zyngier [this message]
2020-07-06 20:05 ` Andy Shevchenko
2020-07-06 17:44 ` Tony Lindgren
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=bfa0f8b35fe5b1864338376fa34b0db1@kernel.org \
--to=maz@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matorola@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=tony@atomide.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