Message-ID: <4A38F229.70504@ahsoftware.de>
Date: Wed, 17 Jun 2009 15:39:53 +0200
From: Alexander Holler <holler@ahsoftware.de>
User-Agent: Thunderbird 2.0.0.19 (X11/20090208)
MIME-Version: 1.0
To: linux-kernel@vger.kernel.org
Subject: asynchronous calls an the lack of --wait-for-completion options (e.g.
 modprobe, losetup, cryptsetup)
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1699
Lines: 48

Hello,

during the last kernel versions I've got more and more problems with
scripts which are calling modprobe, losetup or e.g. cryptsetup.

The problem is that when I'm e.g. calling modprobe loop, loop might not
has finished it's initialization, when modprobe returns.

This leads me to such ugly scripts like
-----------------------------
if [ ! -b /dev/loop0 ]; then
   modprobe loop
   for i in $(seq 1 10) ; do
     if [ -b /dev/loop0 ]; then
       break;
     fi
     sleep 1
   done
fi
do something with /dev/loop0
-----------------------------

which leaves me in doubt if /dev/loop0 really is usable (or if the
module really has finished it's initialization) if /dev/loop0 appeared
(besides the unecessary seconds spended to sleep).

So I'm awaiting the time, when cp in "mkdir foo; cp bar foo" will fail,
because mkdir hasn't completed it's operation (but just started it).

My suggestion would be that all those tools should either offer an
option like --wait-for-completion, or, my prefered solution (which I
naively assume as how those userland-tools should behave), they should
by default wait for completion and could offer an option like
--asynchronous for the rare moments one really doesn't care if the
operation has completed when the appropriate userland-tool returns.

Another question could be, how to be sure if, e.g., modprobe loop
succeeded, if it returns while the operation hasn't finished.

Kind regards,

Alexander Holler

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/