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: <20070328163158.658b372a@the-village.bc.nu>
Date:	Wed, 28 Mar 2007 16:31:58 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Paul Fulghum <paulkf@...rogate.com>
Cc:	Stuart MacDonald <stuartm@...necttech.com>,
	"'Oliver Neukum'" <oliver@...kum.org>, linux-kernel@...r.kernel.org
Subject: Re: question on tty open and close

> As long as the new behavior continues to call
> driver->close() if driver->open() succeeds
> then I see no problem.

It breaks if any existing driver is doing no cleanup in ->open() when it
fails but relying upon ->close() being called. That is what needs
auditing first of all.
-
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/