Re: tty_struct curruption

[Andreas S. <an...@sc...>]

ok, some more research, but i still do not understand what really
happens.

the tty_struct which later is found from kdb_keycode and causes
the oops in tty_insert_flip_char() is correctly kfree()d much
earlier, when the tty is shut down at some point. (they seem to
be opened and released all the time for different purposes.)

But in the vc->vc_tty pointer keeps pointing to the old, freed
tty_struct.
where should that pointer be reset, if a tty is released? 

Shouldnt this happen in tty_io.c in release_dev()? this is not
the case in ruby or in Aivils backport to 2.4.