On 10/03/2014 10:26 PM, Francis Moreau wrote:
> On 10/03/2014 09:58 PM, Dale R. Worley wrote:
>>> From: worley@xxxxxxxxxxxx (Dale R. Worley)
>>
>>> Then I detached the loopback device, re-attached it, and this time,
>>> the partition devices were *not* created, and /var/log/messages did
>>> not have the "loop0: p1 p2" message.
>>>
>>> Given that the message starts "kernel:", I suspect that the udev
>>> behavior is triggered by the kernel detecting the partition table, and
>>> that is not happening. So it looks like it's a kernel bug.
>>
>> I tried that again, after updating to kernel 3.14.19-100.fc19.x86_64,
>> and it worked this time.
>
> Well I'm already running 3.14.18, and the problem is still present but
> not systematic.
>
> Here's a script which should trigger the problem:
>
> -----
> while :; do
>
> losetup -P /dev/loop0 disk.raw ||
> exit
>
> test -e /dev/loop0p1 || {
> echo "missing loop partition"
> losetup -d /dev/loop0
> break
> }
> echo -n "losetup worked: "
> ls /dev/loop0*
>
> losetup -d /dev/loop0 ||
> exit
>
> sleep 1
> done
> ----
>
> After looking at the kernel code, the kernel can silently fail to scan
> the partition table. This can happen if another process is already using
> the device and I think udev is the process that can interfere with
> 'losetup -P'.
>
> What do you think ?
Ok, so IMHO I think that losetup(8) should issue its own
ioctl(BLKRRPART) and shouldn't rely on the kernel during the loop setup
since it can fail silently. This way it can check the return value of
ioctl() and moght choose to do it again in case the return value is -EBUSY.
Or indicates in the man page that the -P can fail silently.
Thanks
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
