Re: asynchronous calls an the lack of --wait-for-completion options (e.g. modprobe, losetup, cryptsetup)
From: Alexander Holler
Date: Mon Jun 22 2009 - 08:09:03 EST
On 20.06.2009 21:20, Kay Sievers wrote:
On Fri, Jun 19, 2009 at 02:52, Robert Hancock<hancockrwd@xxxxxxxxx> 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.
Thanks a lot, I already thought it might be udev, but I haven't known
about udevadm.
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.
But I don't want to extend that discussion. I know this is a complex
subject where many parts are involved and many people are having
different views (e.g. at boot time such asynchronous completion is often
wanted).
It would be nice, if at least the userland-tools would document (e.g. in
there examples-section), that a call to udevadm is necessary before
going on and using the (should already created) device-node (at least if
a stable operation on all systems is needed). The problem is, that it
heavily depends on the system how long udev needs and it might often
work without a call to udevadm so many people could miss the need to
call udevadm.
Kind regards,
Alexander Holler
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/