Re: bug in 2.6.22-rc2: loop mount limited to one single iso image

[Ken Chen]

On 5/19/07, Ray Lee <ray-lk@xxxxxxxxxxxxx> wrote:
> Yeah, that's the only one left. I was hoping it wasn't that one, as it
> claimed to have been tested extensively. Guess it wasn't tested with
> udev.
>
> Ken? Ball's in your court. As the patch isn't providing a killer
> feature for 2.6.22, I'd suggest just reverting it for now until the
> issues are ironed out.

The real solution is to have the user space tool to create these
device nodes in advance.

The original loop patch was coded such that when we open a loop device
N, the immediate adjacent device "N + 1" is created.  This will keep
"mount -o loop" happy because it typically does a linear scan to find
a free device.  This might be somewhat hackary, but certainly will be
backward compatible before user space solution is deployed.

However, the code was removed by Al in this commit:

commit 07002e995638b83a6987180f43722a0eb39d4932
Author: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Date:   Sat May 12 16:23:15 2007 -0400

   fix the dynamic allocation and probe in loop.c

   Signed-off-by: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
   Acked-by: Ken Chen <kenchen@xxxxxxxxxx>
   Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
-
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/