All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Doug Anderson <dianders@chromium.org>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	Alan Cox <alan@linux.intel.com>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] TTY: serial_core: Fix crash if agetty() run on non-console serial port
Date: Sat, 08 Oct 2011 10:49:34 +0200	[thread overview]
Message-ID: <4E900E9E.2070604@gmail.com> (raw)
In-Reply-To: <1318024753-15336-1-git-send-email-dianders@chromium.org>

On 10/07/2011 11:59 PM, Doug Anderson wrote:
> The symptoms of the bug showed up if you were running agetty on ttyS0
> but not using ttyS0 as the console= port on the kernel command
> line.  In this case, if you suspended the system you'd get a crash
> on resume.
>
> The specific order of operations that were running:
> * uart_suspend_port() would be called to put the uart in suspend mode
> * a tty hangup would be processed
> * the hangup would call uart_shutdown()
> * ... suspend / resume happens ...
> * uart_resume_port() would be called and run the code in the
>   (port->flags & ASYNC_SUSPENDED) block, which would startup the port
>   (and enable tx again).
> * Since the UART would be available for tx, we'd immediately get
>   an interrupt, eventually calling transmit_chars()
> * The transmit_chars() function would crash.  The first crash would
>   be a dereference of a NULL tty member, but since the port has been
>   shutdown that was just a symptom.

I cannot reproduce this. What uart driver is this with? And where does
it call uart_suspend_port from? Basically, it would mean that it calls
uart_suspend_port while userspace is still running? Or who HUPs the port
(the second point in your list)?

> Signed-off-by: Doug Anderson <dianders@chromium.org>
> ---
>  drivers/tty/serial/serial_core.c |    8 ++++++++
>  1 files changed, 8 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> index a3efbea..668e56a 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -255,6 +255,14 @@ static void uart_shutdown(struct tty_struct *tty, struct uart_state *state)
>  	}
>  
>  	/*
> +	 * It's possible for shutdown to be called after suspend.  Specifically
> +	 * if agetty() is listening to the serial port we get a HUP after the
> +	 * suspend happend (and HUP calls shutdown).  Clear suspended bit so
> +	 * we don't try to resume a port that has been shutdown.
> +	 */
> +	clear_bit(ASYNCB_SUSPENDED, &port->flags);
> +
> +	/*
>  	 * kill off our tasklet
>  	 */
>  	tasklet_kill(&state->tlet);

thanks,
-- 
js

  reply	other threads:[~2011-10-08  8:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-07 21:59 [PATCH] TTY: serial_core: Fix crash if agetty() run on non-console serial port Doug Anderson
2011-10-08  8:49 ` Jiri Slaby [this message]
2011-10-08 15:55   ` Doug Anderson
2011-10-10 20:28     ` Doug Anderson
2011-10-10 20:28       ` Doug Anderson
2011-10-12  0:25 ` [PATCH v2] TTY: serial_core: Fix crash if DCD drop during suspend Doug Anderson
2011-10-12 11:57   ` Alan Cox
2011-10-18 21:21   ` Greg KH
2011-10-19 18:52     ` [PATCH v3] " Doug Anderson

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=4E900E9E.2070604@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=alan@linux.intel.com \
    --cc=dianders@chromium.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.