From: Alexander Nyberg <alexn@telia.com>
To: Andi Kleen <ak@suse.de>
Cc: Ruben Puettmann <ruben@puettmann.net>,
akpm@osdl.org, linux-kernel@vger.kernel.org, rddunlap@osdl.org
Subject: Re: 2.6.11.7 kernel panic on boot on AMD64
Date: Fri, 29 Apr 2005 22:11:56 +0200 [thread overview]
Message-ID: <1114805516.7659.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20050429144501.GH21080@wotan.suse.de>
> Ok. If you really had such a overlong command line it is ok.
>
> We should probably check this condition better too and error out.
>
How about something like this then (I was thinking making it a panic but
not sure). I think it's a good idea to give some kind of indication so
that there is at least some message when the user discovers that some
things specified on cmdline don't start/work.
Check if the user specified a too long kernel command line and warn
about it being truncated.
Signed-off-by: Alexander Nyberg <alexn@telia.com>
Index: linux-2.6/init/main.c
===================================================================
--- linux-2.6.orig/init/main.c 2005-04-26 11:41:57.000000000 +0200
+++ linux-2.6/init/main.c 2005-04-29 20:28:44.000000000 +0200
@@ -456,6 +456,8 @@
build_all_zonelists();
page_alloc_init();
printk(KERN_NOTICE "Kernel command line: %s\n", saved_command_line);
+ if (strlen(saved_command_line) == COMMAND_LINE_SIZE-1)
+ printk(KERN_ALERT "WARNING: Too long command line! Truncated.\n");
parse_early_param();
parse_args("Booting kernel", command_line, __start___param,
__stop___param - __start___param,
next prev parent reply other threads:[~2005-04-29 20:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 14:03 2.6.11.7 kernel panic on boot on AMD64 Ruben Puettmann
2005-04-27 22:27 ` Randy.Dunlap
2005-04-28 9:05 ` Ruben Puettmann
2005-04-28 15:43 ` Randy.Dunlap
2005-04-28 15:53 ` Ruben Puettmann
2005-04-28 16:38 ` Coywolf Qi Hunt
2005-04-28 16:47 ` Randy.Dunlap
2005-04-29 14:29 ` Andi Kleen
2005-04-29 14:44 ` Ruben Puettmann
2005-04-29 8:25 ` Ruben Puettmann
2005-04-27 23:40 ` Randy.Dunlap
2005-04-29 10:06 ` Alexander Nyberg
2005-04-29 10:10 ` Andrew Morton
2005-04-29 11:10 ` Ruben Puettmann
2005-04-29 11:45 ` Alexander Nyberg
2005-04-29 14:34 ` Andi Kleen
2005-04-29 14:32 ` Andi Kleen
2005-04-29 14:41 ` Ruben Puettmann
2005-04-29 14:45 ` Andi Kleen
2005-04-29 20:11 ` Alexander Nyberg [this message]
2005-05-02 16:42 ` Andi Kleen
2005-04-29 14:44 ` Alexander Nyberg
2005-04-29 14:46 ` Andi Kleen
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=1114805516.7659.2.camel@localhost.localdomain \
--to=alexn@telia.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=ruben@puettmann.net \
/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.