linux-kernel - Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev tmpfs

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: <20090507144353.GA7603@mit.edu>
Date:	Thu, 7 May 2009 10:43:53 -0400
From:	Theodore Tso <tytso@....edu>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Greg KH <greg@...ah.com>, Jan Blunck <jblunck@...e.de>
Subject: Re: [PATCH] driver-core: devtmpfs - driver core maintained /dev
	tmpfs

On Thu, May 07, 2009 at 11:28:19AM +0200, Kay Sievers wrote:
> On Thu, May 7, 2009 at 10:17, Eric W. Biederman <ebiederm@...ssion.com> wrote:
> 
> > sysfs is slow.
> > udev is slow.
> 
> Everything is "slow" if you want to boot "fast". It's just numbers,
> and this is more about simplicity and reliability, with just the side
> effect that it's the fastest you can do, when you don't want to lose
> current functionality.

How much of this is because, say, udev is using shell scripts as
opposed to C?  If the answer is you lose flexibility when you do it as
shell script fragments, I just spent 30 minutes with Alsadair chewing
on my ear about how udev's use of shell scripts is making dm/LVM's
life hard --- and I'll note that if we solve this problem by bloating
the kernel, you lose flexibility *anyway* since the kernel code will
be in C and not shell scripts.  :-)

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