Re: tty_io.c - disassociate_ctty attempted to write to tty = NULLquestion/problem?

[Alan Cox]

> Ok - thanks - added a WARN_ON(!tty) right after the second call to 
> get_current_tty() in disassociate_ctty()

Thsats a perfectly valid path. Its whatever is doing the write you need
to catch. Having a NULL current tty is perfectly acceptable.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/