Comment 10 for bug 342902

ok, i think i see the real problem now, after the post to the mailing list, this bug report and a month of unanswered questions on ircnode i finally had this conversation on #ubuntu-kernel (see attachment).
Their point is that since the loop-aes module is not in the upstream, is not a problem (and jari ruusu, the creator, seems to refuse to put it in upstream because he thinks they are "inepts" :D).
And the reason for the kernel configuration change seems to be a little less boot time.
On #ubuntu-devel i also got this explanation:

Keybuk: because we often have no facility to auto-load the loop module when required
Keybuk: and it's not exactly something you'd ever *not* want loaded
Keybuk: that module doesn't contain a driver
Keybuk: so it's not as if we'll ever need to backport a newer version
Keybuk: or blacklist it for hardware issues
Keybuk: it's just a kernel feature
Keybuk: and it makes little sense to have kernel features *not* =y

All reasonable, but now our (the users) problem is that we can't neither recompile the kernel every update, nor try to persuade some people to do anything, you should just get back to CONFIG_BLK_DEV_LOOP=m and let us replace the module as we like, as in a "modular kernel"... (even if this slows the boot by a millisecond)