[lkml]   [2010]   [Nov]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/1] TTY: don't allow reopen when ldisc is changing
On Fri, Nov 26, 2010 at 08:46:18AM +0100, Jiri Slaby wrote:
> >> - if (test_bit(TTY_CLOSING, &tty->flags))
> >> + if (test_bit(TTY_CLOSING, &tty->flags) ||
> >> + test_bit(TTY_LDISC_CHANGING, &tty->flags))
> >> return -EIO;
> >>
> >> if (driver->type == TTY_DRIVER_TYPE_PTY &&
> >
> > Unfortunately, users report this doesn't seem to fix things for them
> > (built against 2.6.36 (plus another patch you wrote iirc.))
> Which patches exactly do you have? You need three of mine in 2.6.36.
> >

Hrm, I'm still seeing it on top of Linus' latest with that patch. :/

Even more bizarrely, I tried to come up with ways this could be failing,
and decided to test a few things...

I set_bit(TTY_DEBUG, &tty->flags) just before returning from
tty_init_dev (which, afaict, should be called for vc/tty$n and ptys?)
and then checked it with a similar WARN_ON in tty_reopen, and found that
I was hitting it fairly regularly.

As far as I can tell, for this to occur, we'd need something to open
/dev/tty1 first, which hits the tty_init_dev, and something else to very
closely follow that, hit the linking of driver->ttys[idx] and so skip
into tty_reopen, and smack into my WARN_ON.

Of course, given the locking, I have no idea how it could possibly be

I'm poking around to see, I think maybe something might be dropping
locks in the callchain that gives us a window where this might be
possible... I don't see any other way we could end up with tty1 having
TTY_LDISC unset.

(I'm poking in some more debugging, and moving the 'linking in' of the
device until after tty_ldisc_setup in tty_init_dev, but I'm not
particularly hopeful.)


 \ /
  Last update: 2010-11-27 04:03    [W:0.071 / U:5.680 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site