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: <4A3AE162.7040407@gmail.com>
Date:	Thu, 18 Jun 2009 18:52:50 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Alexander Holler <holler@...oftware.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: asynchronous calls an the lack of --wait-for-completion options
 (e.g.   modprobe, losetup, cryptsetup)

On 06/17/2009 07:39 AM, Alexander Holler wrote:
> 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.

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..
--
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/