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] [day] [month] [year] [list]
Message-ID: <20090623170141.41fe1565@lxorguk.ukuu.org.uk>
Date:	Tue, 23 Jun 2009 17:01:41 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Kay Sievers <kay.sievers@...y.org>
Cc:	Alexander Holler <holler@...oftware.de>,
	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 Tue, 23 Jun 2009 13:35:07 +0200
Kay Sievers <kay.sievers@...y.org> wrote:

> 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

which unsolves lots of other problems and has good reasons why people
object to it.

Sorting out waiting behaviour and fixing udev to do jobs once is a user
space problem and while it might benefit from some tiny bits of kernel
help re-implementing devfs (which we've been through before thank you) is
not the cure but replacing a minor ailment with a nasty disease
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ