[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b040c32a0703301506q17509843h1309a4132634154a@mail.gmail.com>
Date: Fri, 30 Mar 2007 15:06:03 -0700
From: "Ken Chen" <kenchen@...gle.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: "Jan Engelhardt" <jengelh@...ux01.gwdg.de>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [patch] remove artificial software max_loop limit
On 3/30/07, Andrew Morton <akpm@...ux-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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists