Messages in this thread | | | Date | Sun, 7 Feb 1999 00:17:26 +0100 (MET) | From | (Guest section DW) | Subject | Re: Linux-2.2.2-pre2.. |
| |
[halved the long cc list]
From: Alexander Viro <viro@math.psu.edu> To: Philippe Troin <phil@fifi.org>
On 6 Feb 1999, Philippe Troin wrote:
> Are these 'dev (03:00) tty->count(0) != #fd's(2) in do_tty_hangup' > and 'null tty in fasync' really harmless ?
It means that either you've got a struct file leak or something is playing bad games with filp->private_data. In theory it may be any other subsystem using the same field. IIRC tty code more or less blindly assumes that meaningful value in private_data means that we have a tty-related struct file. Potential candidates: AFFS, CODA(?), drivers/net/cosa.c(?), ISDN, APM(?), MTRR(?). Do you have any of those beasts?
Five years ago we saw precisely the same messages, long before any of your candidates existed as part of a default kernel. Sounds like a flaw in the tty code. I do not know whether it is harmless, but it happens occasionally.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |