loop device

Scott James Remnant scott at canonical.com
Mon Sep 7 16:10:06 UTC 2009

On Mon, 2009-09-07 at 05:57 -0400, Pete Graner wrote:

> Eugene Gorodinsky wrote:
> > Sorry, I meant nobody had stated the reasons for compiling the loop
> > device into the kernel. Or was that the reason to compile it in rather
> > than the reason to not compile it in?
> It was done primarily as an effort to link in all common modules across 
> all kernels. It was perhaps an oversight since increasing loop devs is a 
> real need.

It's compiled in because we have no method for on-demand loading of this
module.  If you don't compile it in, loop devices will fail to mount
unless you run "modprobe loop" somewhere.

I don't see any reason why this module cannot expose its configuration
parameter in /sys to be adjustable at run time.  Better still, source
the LKML patches to make loop devices simply dynamic (so we don't always
have a fixed number).

Scott James Remnant
scott at canonical.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/kernel-team/attachments/20090907/89e96f4a/attachment.sig>

More information about the kernel-team mailing list