From: bert hubert <ahu@ds9a.nl>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Kconfig allows LOG_BUF_SHIFT parameters that lead to disfunctional kernel
Date: Wed, 2 Jul 2003 15:02:58 +0200 [thread overview]
Message-ID: <20030702130258.GA14640@outpost.ds9a.nl> (raw)
[also sent to akpm in a separate message that was posted to
'linus-kernel@vger.kernel.org by accident]
Attached patch adds a range check to LOG_BUF_SHIFT and clarifies the
configuration somewhat. I managed to build a non-booting kernel because I
thought 64 was a nice power of two, which lead to the kernel blocking when
it tried to actually use or allocate a 2^64 buffer.
Please apply, would've saved me a few hours of debugging.
--- init/Kconfig~ 2003-07-02 14:49:28.000000000 +0200
+++ init/Kconfig 2003-07-02 14:40:53.000000000 +0200
@@ -93,7 +93,8 @@
limited in memory.
config LOG_BUF_SHIFT
- int "Kernel log buffer size" if DEBUG_KERNEL
+ int "Kernel log buffer size (16 => 64KB, 17 => 128KB)" if DEBUG_KERNEL
+ range 12 20
default 17 if ARCH_S390
default 16 if X86_NUMAQ || IA64
default 15 if SMP
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
reply other threads:[~2003-07-02 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030702130258.GA14640@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--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®