linux-kernel - Re: [PATCH] Driver Core: devtmpfs - kernel-maintained tmpfs-based /dev

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]

Date:	Tue, 11 Aug 2009 20:25:27 -0400
From:	David Dillow <dave@...dillows.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Greg KH <greg@...ah.com>, Greg KH <gregkh@...e.de>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	linux-kernel@...r.kernel.org, Kay Sievers <kay.sievers@...y.org>,
	Jan Blunck <jblunck@...e.de>, Harald Hoyer <harald@...hat.com>,
	Scott James Remnant <scott@...ntu.com>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH] Driver Core: devtmpfs - kernel-maintained tmpfs-based
 /dev

On Tue, 2009-08-11 at 16:55 +0200, Andi Kleen wrote:
> > No, not really. It isn't hard to make a static /dev, or a rescue initrd
> > for the cases with dynamic device numbers.
> 
> There's a world between strictly controlled embedded and fully general
> distributions.

Sure, and I've acknowledged that. But it doesn't mean this needs a
kernel solution.

> I want a dynamic /dev, but a fast one that doesn't need initrd or
> slows down booting.

So use Eric/Arjan's program that does it in 60ms -- you get a
dynamic /dev, no initrd, fast boot, and no kernel changes required.

It remains to be seen how much it costs to do it in user space vs kernel
space. Arjan -- do you have a pointer to your program? Perhaps I can
shake loose some time to test that.

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