From: "Randy.Dunlap" <rddunlap@osdl.org>
To: <rddunlap@osdl.org>
Cc: <76306.1226@compuserve.com>, <linux-kernel@vger.kernel.org>
Subject: Re: Wanted: a limit on kernel log buffer size
Date: Sun, 6 Apr 2003 20:35:59 -0700 (PDT) [thread overview]
Message-ID: <33271.4.64.238.61.1049686559.squirrel@webmail.osdl.org> (raw)
In-Reply-To: <33182.4.64.238.61.1049683748.squirrel@webmail.osdl.org>
>> Some people (who will mercifully go unnamed) just will _not_
>> read the documentation, and set the kernel log buffer shift
>> to 31 on a 256MB machine. This attempt to allocate 2GB of memory for the
>> buffer results in an unbootable kernel.
>>
>> Suggestions?
>
> This is a multi-part answer. Say, 5 parts.
>
> 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'm inserting it here via cut-and-paste, so it might not be all clean.
Patch is to 2.5.66-PV (plain vanilla).
patch_name: logbuf-limit.patch
patch_version: 2003-04-06.20:28:43
author: Randy.Dunlap <rddunlap@osdl.org>
description: limit kernel log buffer size to 1 MB
product: Linux
product_versions: 2.5.66
diffstat: =
kernel/printk.c | 3 +++
1 files changed, 3 insertions(+)
diff -Naur ./kernel/printk.c%LBLIM ./kernel/printk.c
--- ./kernel/printk.c%LBLIM 2003-04-06 20:27:28.000000000 -0700
+++ ./kernel/printk.c 2003-04-06 20:27:53.000000000 -0700
@@ -34,6 +34,9 @@
#define LOG_BUF_LEN (1 << CONFIG_LOG_BUF_SHIFT)
#define LOG_BUF_MASK (LOG_BUF_LEN-1)
+#if (CONFIG_LOG_BUF_SHIFT > 20)
+#error CONFIG_LOG_BUF_SHIFT is ridiculously large (more than 1 MB).
+#endif
/* printk's without a loglevel use this.. */
#define DEFAULT_MESSAGE_LOGLEVEL 4 /* KERN_WARNING */
next prev parent reply other threads:[~2003-04-07 3:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 1:34 Chuck Ebbert
2003-04-07 2:49 ` Randy.Dunlap
2003-04-07 3:35 ` Randy.Dunlap [this message]
2003-04-07 3:39 ` Robert Love
2003-04-07 4:32 ` Randy.Dunlap
2003-04-07 23:17 ` [PATCH] " Randy.Dunlap
2003-04-07 12:19 ` Roman Zippel
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=33271.4.64.238.61.1049686559.squirrel@webmail.osdl.org \
--to=rddunlap@osdl.org \
--cc=76306.1226@compuserve.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®