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: <ac3eb2510906201220v7fc1d51ve4a9937a3d73d3d4@mail.gmail.com>
Date:	Sat, 20 Jun 2009 21:20:11 +0200
From:	Kay Sievers <kay.sievers@...y.org>
To:	Robert Hancock <hancockrwd@...il.com>
Cc:	Alexander Holler <holler@...oftware.de>,
	linux-kernel@...r.kernel.org
Subject: Re: asynchronous calls an the lack of --wait-for-completion options 
	(e.g. modprobe, losetup, cryptsetup)

On Fri, Jun 19, 2009 at 02:52, Robert Hancock<hancockrwd@...il.com> wrote:
> On 06/17/2009 07:39 AM, Alexander Holler wrote:

>> The problem is that when I'm e.g. calling modprobe loop, loop might not
>> has finished it's initialization, when modprobe returns.
>
> It will have. Just that udev won't have received the events and created the
> device node yet. So the solution would likely be on the udev side..

The brutal method to do this is to call:
  udevadm settle
after loading the module. It will block until all currently pending
events for udev are fully handled.

Recent udevadm versions also have a:
  --exit-if-exists=<filename>
option, which will make "settle" stop waiting if a given file exists.

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/