On Tue, Nov 27, 2012 at 10:53:57AM +0100, Sebastian Andrzej Siewior wrote:
> On Wed, Nov 21, 2012 at 02:04:26PM +, Alan Cox wrote:
> > > I don't see any problems in my testcase.
> >
> > This looks fine to me as by the time we call tty_ldisc_release we have
> > already set TTY_CLOSING on both s
On Wed, Nov 21, 2012 at 02:04:26PM +, Alan Cox wrote:
> > I don't see any problems in my testcase.
>
> This looks fine to me as by the time we call tty_ldisc_release we have
> already set TTY_CLOSING on both sides.
Greg, can you push this into v3.7? This regression has been introduced in
v3.7
> I don't see any problems in my testcase.
This looks fine to me as by the time we call tty_ldisc_release we have
already set TTY_CLOSING on both sides.
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordom
Since commit 89c8d91e31f2 ("tty: localise the lock") I see a dead lock
in one of my dummy_hcd + g_nokia test cases. The first run one was usually
okay, the second often resulted in a splat by lockdep and the third was
usually a dead lock.
Lockdep complained about tty->hangup_work and tty->legacy_mu
