linux-kernel - Re: asynchronous calls an the lack of --wait-for-completion options (e.g. modprobe, losetup, cryptsetup)

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: <ac3eb2510906230435r6489ddafqb15214f190d4eae8@mail.gmail.com>
Date:	Tue, 23 Jun 2009 13:35:07 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Alexander Holler <holler@...oftware.de>
Cc:	Robert Hancock <hancockrwd@...il.com>,
	linux-kernel@...r.kernel.org, Greg Kroah-Hartmann <greg@...ah.com>
Subject: Re: asynchronous calls an the lack of --wait-for-completion options 
	(e.g. modprobe, losetup, cryptsetup)

On Mon, Jun 22, 2009 at 14:08, Alexander Holler<holler@...oftware.de> wrote:
> On 20.06.2009 21:20, Kay Sievers wrote:

> Anyway, I still think, that the creation of the device-node is (seen from a
> user-point) part of the module-initialization or part of the operation of
> the userland-tool (like modprobe, losetup or cryptsetup). So in my point of
> view, they should at least offer an option to wait until udev finished that
> operation and should not rely on the user to call udevadm.

That would be all solved properly by "devtmpfs":
   http://lkml.org/lkml/2009/4/30/182

You might want to talk to the people who are delaying its adoption.

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/