From: Bernhard Walle <bwalle@suse.de>
To: kexec@lists.infradead.org
Subject: Re: Kexec command line length
Date: Mon, 28 Jan 2008 22:29:10 +0100 [thread overview]
Message-ID: <20080128212910.GA21889@suse.de> (raw)
In-Reply-To: <20080128205324.GC1174@hmsreliant.think-freely.org>
* Neil Horman <nhorman@tuxdriver.com> [2008-01-28 21:53]:
> return -1;
> }
>
> + if (setup_header.protocol_version >= 0x0206) {
> + if (command_line_len > setup_header.cmdline_size) {
> + dbgprintf("Kernel command line too long for kernel!\n");
> + return -1;
> + }
> + }
> +
> if (setup_header.protocol_version >= 0x0205) {
> relocatable_kernel = setup_header.relocatable_kernel;
> dbgprintf("bzImage is relocatable\n");
I know that there was a kernel release with 2048 _and_ still the old
boot protocol, but wouldn't it be better to warn the user if the size
is beyond 256 and the old kernel is used? I think new kexec-tools
should still support old kernels without problems ...
Bernhard
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-01-28 21:29 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-14 13:43 Kexec command line length Neil Horman
2008-01-14 14:50 ` Bernhard Walle
2008-01-14 15:40 ` Neil Horman
2008-01-15 15:27 ` Vivek Goyal
2008-01-15 17:09 ` Neil Horman
2008-01-15 17:37 ` Vivek Goyal
2008-01-25 12:35 ` Neil Horman
2008-01-25 15:39 ` Vivek Goyal
2008-01-25 15:44 ` H. Peter Anvin
2008-01-25 19:50 ` Neil Horman
2008-01-25 19:54 ` H. Peter Anvin
2008-01-25 20:11 ` Neil Horman
2008-01-25 20:13 ` Vivek Goyal
2008-01-25 20:54 ` Neil Horman
2008-01-28 17:08 ` Neil Horman
2008-01-28 19:37 ` Vivek Goyal
2008-01-28 20:07 ` Neil Horman
2008-01-28 20:20 ` Vivek Goyal
2008-01-28 20:53 ` Neil Horman
2008-01-28 21:09 ` Vivek Goyal
2008-01-28 21:29 ` Bernhard Walle [this message]
2008-01-29 1:01 ` Neil Horman
2008-01-29 15:41 ` Vivek Goyal
2008-01-29 18:17 ` Bernhard Walle
2008-01-29 18:52 ` Neil Horman
2008-01-29 19:57 ` Neil Horman
2008-01-30 20:53 ` Vivek Goyal
2008-01-30 20:59 ` Neil Horman
2008-01-30 21:08 ` Vivek Goyal
2008-01-30 21:18 ` Neil Horman
2008-01-30 21:45 ` Vivek Goyal
2008-01-31 0:10 ` Neil Horman
2008-01-31 7:16 ` Bernhard Walle
2008-02-12 21:11 ` Neil Horman
2008-02-18 3:14 ` Simon Horman
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=20080128212910.GA21889@suse.de \
--to=bwalle@suse.de \
--cc=kexec@lists.infradead.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