Subject: Re: revoke(2), /dev/console and /dev/ttyE0
To: <>
From: David Laight <david@l8s.co.uk>
List: tech-kern
Date: 10/15/2003 00:26:30
> > > What's supposed to happen is that the revoke on one of the nodes will 
> > > wander through vgonel(), and then to vclean(, DOCLOSE, ), and eventually 
> > > to a VOP_CLOSE() call on the underlying device. If that close happens on 
> > > the console device, it will end up closing the underlying device.
> > 
> > The VOP_VLOSE() on the underlying device only happens on the last close.
> 
> Are you sure of that? Look at spec_close() and remember that when we're in 
> vclean(), VXLOCK will be set:

That is true for /dev/console, but not when the cons code releases
/dev/ttyE0 - which is the device that needs its close routine called.
 
> > If something else has it open, that doesn't happen - so the tty->t_session
> > stuff doesn't get zapped.
> 
> I think your other note hit this problem on the head. Though I feel a bit 
> rusty around some of the tty subsystem, so please have someone else look 
> at it too. :-)

Any volunteers ?

	David

-- 
David Laight: david@l8s.co.uk