lkml.org 
[lkml]   [2007]   [Mar]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] remove artificial software max_loop limit
On 3/30/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> So.. this change will cause a fatal error for anyone who is presently
> using max_loop, won't it? If they're doing that within their
> initramfs/initrd/etc then things could get rather ugly for them.

probably, if they access loop device non-sequentially.


> I don't know how much of a problem this will be in practice - do people use
> max_loop much?

I don't know either.


> btw, did you test this change as both a module and as linked-into-vmlinux?

as linked-into-vmlinux. why do you ask? It breaks if it is module?
I made last minute change to a mutex name and shamely posted without
doing a compile test. Besides that, is there something else breaks?

- Ken
-
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-03-31 00:09    [W:0.184 / U:0.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site