linux-kernel - Re: question on tty open and close

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070328154439.40ca5c3c@the-village.bc.nu>
Date:	Wed, 28 Mar 2007 15:44:39 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Stuart MacDonald" <stuartm@...necttech.com>
Cc:	"'Oliver Neukum'" <oliver@...kum.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: question on tty open and close

> > > > So we have a file that's closed although open() never succeeded?
> > > 
> > > That's correct! It's been a pain in my butt for years.
> > 
> > How did you deal with that proctological issue?
> 
> Just make sure the close() handles the situation properly. It makes
> reference counting...  fun.
> 
> The serial driver has always handled it like this.

I'm also not aware of any reason other than history, which means if
someone cares to double check the other drivers there really shouldn't be
an obstacle to "fixing" this behaviour.

Unless anyone knows different ?

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