linux-kernel - Re: [RFC][PATCH] init: Open /dev/console from rootfs

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] [day] [month] [year] [list]

Date:	Wed, 03 Mar 2010 12:07:15 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Al Viro <viro@...IV.linux.org.uk>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [RFC][PATCH] init: Open /dev/console from rootfs

On 03/03/2010 11:57 AM, Al Viro wrote:
> On Tue, Mar 02, 2010 at 11:53:19PM -0800, Eric W. Biederman wrote:
>>
>> To avoid potential problems with an empty /dev open /dev/console
>> from rootfs instead of waiting to mount our root filesystem and
>> mounting it there.   This effectively guarantees that there will
>> be a device node, and it won't be on a filesystem that we will
>> ever unmount, so there are no issues with leaving /dev/console
>> open and pinning the filesystem.
>>
>> This is actually more effective than automatically mounting
>> devtmpfs on /dev because it removes removes the occasionally
>> problematic assumption that /dev/console exists from the boot
>> code.
> 
> Hell, yeah.  Applied, with thanks.

:) :)

	-hpa

--
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/