From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>, Rob Herring <robh@kernel.org>,
Peter Hurley <peter@hurleysoftware.com>,
Alan Cox <alan@linux.intel.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tty: serial_core: Fix serial console crash on port shutdown
Date: Wed, 19 Oct 2016 10:17:06 +0200 [thread overview]
Message-ID: <20161019081706.GC8106@bigcity.dyn.berto.se> (raw)
In-Reply-To: <1476808540-2757-1-git-send-email-geert+renesas@glider.be>
Hi Geert,
On 2016-10-18 18:35:40 +0200, Geert Uytterhoeven wrote:
> The port->console flag is always false, as uart_console() is called
> before the serial console has been registered.
>
> Hence for a serial port used as the console, uart_tty_port_shutdown()
> will still be called when userspace closes the port, powering it down.
> This may lead to a system lock up when the serial console driver writes
> to the serial port's registers.
>
> To fix this, move the setting of port->console after the call to
> uart_configure_port(), which registers the serial console.
>
> Fixes: 761ed4a94582ab29 ("tty: serial_core: convert uart_close to use tty_port_close")
> Reported-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Acked-by: Rob Herring <robh@kernel.org>
It fixes the issue I was seeing with systemd as a init system.
Tested-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
> ---
> v2:
> - Add Acked-by,
> - Reworded one-line summary (incl. magic word "fix").
>
> Can easily be reproduced on Renesas boards:
> 1. With systemd: hangs during boot,
> 2. Without systemd: "telinit n" to switch to a runlevel that doesn't
> run a getty on ttySC0, and trigger kernel console output => hang.
> ---
> drivers/tty/serial/serial_core.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> index 6e4f63627479db8d..ce8899c13af3d97f 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -2746,8 +2746,6 @@ int uart_add_one_port(struct uart_driver *drv, struct uart_port *uport)
> uport->cons = drv->cons;
> uport->minor = drv->tty_driver->minor_start + uport->line;
>
> - port->console = uart_console(uport);
> -
> /*
> * If this port is a console, then the spinlock is already
> * initialised.
> @@ -2761,6 +2759,8 @@ int uart_add_one_port(struct uart_driver *drv, struct uart_port *uport)
>
> uart_configure_port(drv, state, uport);
>
> + port->console = uart_console(uport);
> +
> num_groups = 2;
> if (uport->attr_group)
> num_groups++;
> --
> 1.9.1
>
--
Regards,
Niklas Söderlund
prev parent reply other threads:[~2016-10-19 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 16:35 [PATCH v2] tty: serial_core: Fix serial console crash on port shutdown Geert Uytterhoeven
2016-10-19 8:06 ` [v2] " Mugunthan V N
2016-10-19 8:17 ` Niklas Söderlund [this message]
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=20161019081706.GC8106@bigcity.dyn.berto.se \
--to=niklas.soderlund@ragnatech.se \
--cc=alan@linux.intel.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).