All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: "Ken Chen" <kenchen@google.com>
Cc: "Jan Engelhardt" <jengelh@linux01.gwdg.de>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [patch] remove artificial software max_loop limit
Date: Fri, 30 Mar 2007 14:15:24 -0700	[thread overview]
Message-ID: <20070330141524.5f6cff29.akpm@linux-foundation.org> (raw)
In-Reply-To: <b040c32a0703300225r3f8b1daah2f95e8af26c0d867@mail.gmail.com>

On Fri, 30 Mar 2007 02:25:37 -0700
"Ken Chen" <kenchen@google.com> wrote:

> -module_param(max_loop, int, 0);
> -MODULE_PARM_DESC(max_loop, "Maximum number of loop devices (1-256)");

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.

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

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

  parent reply	other threads:[~2007-03-30 21:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-30  7:53 [patch] remove artificial software max_loop limit Ken Chen
2007-03-30  8:48 ` Ken Chen
2007-03-30  9:07   ` Jan Engelhardt
2007-03-30  9:25     ` Ken Chen
2007-03-30 16:16       ` Jan Engelhardt
2007-03-30 21:15       ` Andrew Morton [this message]
2007-03-30 22:06         ` Ken Chen
2007-03-30 22:50           ` Andrew Morton
2007-03-31 17:07         ` Greg KH
2007-03-31 17:41           ` Andrew Morton
2007-04-01  4:16             ` Ken Chen
2007-04-04 10:31               ` Tomas M
2007-04-04 18:47                 ` Andrew Morton
2007-04-01 16:53         ` Tomas M
2007-04-01 16:57           ` Tomas M
2007-04-01 18:10             ` Ken Chen
2007-04-01 19:06               ` Jan Engelhardt
2007-04-06 20:33                 ` Bill Davidsen
2007-04-07 16:18                   ` Valdis.Kletnieks
2007-04-07 16:34                     ` Bill Davidsen
2007-03-30 21:46       ` Andrew Morton
2007-03-30 21:52         ` Jan Engelhardt
  -- strict thread matches above, loose matches on Subject: below --
2007-04-01  9:16 devzero
2007-04-01 10:53 devzero
2007-04-01 18:03 ` Ken Chen
2007-04-01 19:00 ` Jeff Dike
2007-04-01 18:36 devzero
2007-04-01 18:43 ` Kyle Moffett
2007-04-01 18:54 devzero

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070330141524.5f6cff29.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=kenchen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.