All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: 76306.1226@compuserve.com, linux-kernel@vger.kernel.org
Subject: Re: Wanted: a limit on kernel log buffer size
Date: 06 Apr 2003 23:39:54 -0400	[thread overview]
Message-ID: <1049686794.894.13.camel@localhost> (raw)
In-Reply-To: <33271.4.64.238.61.1049686559.squirrel@webmail.osdl.org>

On Sun, 2003-04-06 at 23:35, Randy.Dunlap wrote:

> > a.  If someone won't read the help text, how can we help them?
> >
> > b.  If we make a 2 GB log buffer size a compile-time error, will
> > they read that?
> >
> > c.  If we make it a compile-time warning, will they read that?
> >
> > d.  What limit(s) do you suggest?  I can try to add some limits.
> >
> > e.  This kind of config limiting should be done in the config system IMO.
> > I've asked Roman for that capability....
> 
> Here's a patch that limits kernel log buffer size to 1 MB max.
> Comments?

I liked points (a) and (e) above.

I say if users cannot bother to read the documentation and understanding
things, why are they compiling a kernel?

And if we are going to implement parameters bounds checking it should be
done in kconfig.  There are a few other places that want it, too.

	Robert Love


  reply	other threads:[~2003-04-07  3:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07  1:34 Wanted: a limit on kernel log buffer size Chuck Ebbert
2003-04-07  2:49 ` Randy.Dunlap
2003-04-07  3:35   ` Randy.Dunlap
2003-04-07  3:39     ` Robert Love [this message]
2003-04-07  4:32       ` Randy.Dunlap
2003-04-07 23:17     ` [PATCH] " Randy.Dunlap
2003-04-07 12:19   ` Roman Zippel
  -- strict thread matches above, loose matches on Subject: below --
2003-04-07  8:55 Chuck Ebbert
2003-04-07 16:24 ` Randy.Dunlap
2003-04-07  8:55 Chuck Ebbert
2003-04-07 21:12 Chuck Ebbert

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=1049686794.894.13.camel@localhost \
    --to=rml@tech9.net \
    --cc=76306.1226@compuserve.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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.