![]() | |||||||||||||
Messages in this thread |
On 5/21/07, Linus Torvalds <torvalds@linux-foundation.org> wrote: > Yes. Can somebody who actually _uses_ loop send a tested patch, please? > > We're not going to break existing user space over something idiotic like > this. Not acceptable. > > The alternative is to just revert all the loop.c patches. Which I'll do > unless somebody sends me a tested fix - because as a non-loop user myself, > I don't have much choice. I assume it is > > commit 73285082 "remove artificial software max_loop limit" > > that introduced the new behaviour. Ken? yes and no. in that commit, I automatically create n+1 device when loop device n is created, allergically was tested to be fine with casual usage of "losetup" and "mount -o loop". However, there is a bug in that commit when loop.c was compiled as a module. And when Al fixed it, he also removed that magic "n+1" trick. Nevertheless, yes, I'm guilty of introducing the new behavior. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2007-05-21 18:31 [from the cache] ©2003-2008 | |||||||||||||