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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 10 May 2009 02:56:44 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	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 Sun, May 10, 2009 at 02:29, Eric W. Biederman <ebiederm@...ssion.com> wrote:
> Kay Sievers <kay.sievers@...y.org> writes:
>
>> 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.
>
> My primary concern is that you are inventing a new mechanism when
> the existing mechanism has known issues that could explain the slowdowns.

You mean that mounting a new tmpfs at /dev has the issue of being
empty? And it takes time to fill it, where you can't reliably do other
things at the same time that might need device nodes? Yeah, I guess
that's an issue with the existing mechanism, and I'm interested in
your proposal to solve it.

Thanks,
Kay
--
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/