Re: Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open

• Next message: Linus Torvalds: "Re: [PATCH] (0/8) replace brlock with RCU"
• Previous message: David S. Miller: "Re: [PATCH] (2/8) Eliminate brlock for packet_type"
• In reply to: Martin J. Bligh: "Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open"
• Next in thread: Andrew Morton: "Re: Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Tue, 2003-03-11 at 23:49, Martin J. Bligh wrote:
> I'm getting lots of these messages whilst running big SDET runs on
> an 16-way machine ... anyone recognize them?
> (64-bk3 + a few patches).
>
> dev (pts(136,0)) tty->count(4) != #fd's(3) in release_dev
> Warning: dev (pts(136,0)) tty->count(4) != #fd's(3) in tty_open
> Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open
> Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in release_dev

These are some of the things I saw when reporting the tty races and
doing zillions of open/closes on pty/tty pairs. The tty layer has
some fun code dealing with open v close v hangup v vhangup

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

• Next message: Linus Torvalds: "Re: [PATCH] (0/8) replace brlock with RCU"
• Previous message: David S. Miller: "Re: [PATCH] (2/8) Eliminate brlock for packet_type"
• In reply to: Martin J. Bligh: "Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open"
• Next in thread: Andrew Morton: "Re: Warning: dev (pts(136,0)) tty->count(5) != #fd's(4) in tty_open"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Mar 15 2003 - 22:00:28 EST