On Wed, Jan 18, 2012 at 13:13, Karel Zak <kzak@xxxxxxxxxx> wrote: > On Tue, Jan 17, 2012 at 10:59:59PM -0300, Gerardo Exequiel Pozzi wrote: >> Using (losetup from util-linux 2.20.620-4360-dirty) and Linux-3.2.1. >> >> Using losetup as first time, if loop module is not loaded, losetup -f >> file-equal-or-below-1MiB I get: "Buffer I/O error on device loop0, logical >> block 0" (sometimes get one message, or two or three, ...) > > It does not sound like userspace problem, I guess that the message comes > from kernel (dmesg). It would be also nice to have strace output. > >> >> Can be reproducible again if loop module is unloaded then execute losetup. >> Does not happen if module is loaded previously to losetup. >> Happens independently if /dev/loop0 exists or not. >> >> Does not happen with losetup from 2.20 under the same conditions. > > The new losetup uses /dev/loop-control to get the new free loop device. > > Kay, any idea? No really. Accessing /dev/loop-control should block losetup, and synchronously load the look.ko module, before doing any further operation in losetup. Kay -- 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
