[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
The following reply was made to PR kern/46522; it has been noted by GNATS.
From: christos%zoulas.com@localhost (Christos Zoulas)
To: gnats-bugs%NetBSD.org@localhost, kern-bug-people%netbsd.org@localhost,
Subject: Re: kern/46522
Date: Mon, 4 Jun 2012 09:14:56 -0400
On Jun 4, 9:15am, david%l8s.co.uk@localhost (David Laight) wrote:
-- Subject: Re: kern/46522
| While adding a fixed sleep is enough to show where the problem
| lies, it isn't an appropriate solution to the problem.
| You need to properly wait for the close to release a reference
| count on the resource, and then free the relevant data areas.
| The scheduler can always decide to not run the process you
| are waiting for - so the sleep has to be indefinitely long.
| I;m not saying a real fix is easy! the tty subsystem is full
| of places where it isn't remotely MP-safe.
What's the plan here? Is the getty process supposed to be killed, and if
so by whom? I would prefer if instead it got an EOF from the tty and
then it was waited until it exited before the screen was destroyed.
Main Index |
Thread Index |