[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120914114917.3ae5680d@pyramind.ukuu.org.uk>
Date: Fri, 14 Sep 2012 11:49:17 +0100
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: Alexey Khoroshilov <khoroshilov@...ras.ru>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel@...r.kernel.org, ldv-project@...ras.ru
Subject: Re: [PATCH] pcmcia: synclink_cs: fix potential tty NULL dereference
On Fri, 14 Sep 2012 01:30:06 +0400
Alexey Khoroshilov <khoroshilov@...ras.ru> wrote:
> tty_port_tty_get() can return NULL after port hangup that may happen anytime.
> The patch adds checks that tty_port_tty_get() returns nonNULL around places
> where tty is actually used.
I don't believe you can simply skip the processing in this case howevver
on the rx side. You are no longer reading the state, draining the FIFO
etc. Have you tested this on actual hardware and faked the tty = NULL
case ?
The tx one looks better.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists