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:	Wed, 12 Aug 2009 10:39:57 -0400
From:	David Dillow <dave@...dillows.org>
To:	Greg KH <greg@...ah.com>
Cc:	Andi Kleen <andi@...stfloor.org>, 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 Wed, 2009-08-12 at 06:44 -0700, Greg KH wrote:
> On Wed, Aug 12, 2009 at 08:56:53AM -0400, David Dillow wrote:
> > On Tue, 2009-08-11 at 17:34 -0700, Greg KH wrote:
> > > On Tue, Aug 11, 2009 at 08:25:27PM -0400, David Dillow wrote:
> > > > 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.
> > > 
> > > Their program only handles it for a reconstruction of /dev based on
> > > sysfs one time at boot.  It does not handle things that are added or
> > > discovered by the system after that, you need udev for that.
> > > 
> > > So it's a great hack for boot time stuff, but not a complete /dev
> > > management replacement like this code can be for numerous systems.
> > 
> > What systems would those be?
> 
> Rescue disks, Embedded systems with no local users, servers with no
> local users, etc.  Basically anything that you are only root on, and
> don't care about group permissions.

We've discussed those, though, and I think most of those fall under
either having full control of their static environment, or would have
something to watch for hotplug events -- udev or a replacement -- and so
would have the ability to create the node from user space.

Rescue disks may be an exception, but they only need a minimal
static /dev and then run a tool to get the initial setup. If you are
expecting an expert to use them, then either running the tool by hand or
as a post-modprobe rule should catch updates. They can also run udev (or
a replacement) with stripped rules if you want to make it friendlier to
non-expert users.


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