From: "H. Peter Anvin" <hpa@zytor.com>
To: Matthew Garrett <mjg59@srcf.ucam.org>, Yinghai Lu <yinghai@kernel.org>
Cc: Matthew Garrett <matthew.garrett@coreos.com>,
Ingo Molnar <mingo@kernel.org>,
the arch/x86 maintainers <x86@kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@coreos.com>
Subject: Re: [PATCH V2] x86: Allow built-in command line to work in early kernel init
Date: Tue, 12 May 2015 19:46:11 -0700 [thread overview]
Message-ID: <5552BAF3.7040605@zytor.com> (raw)
In-Reply-To: <20150512235333.GB1437@srcf.ucam.org>
On 05/12/2015 04:53 PM, Matthew Garrett wrote:
> On Tue, May 12, 2015 at 04:41:22PM -0700, Yinghai Lu wrote:
>
>> You can not assume that you can use buffer after cmd_line from bootloader
>> blindly.
>
> Are there any bootloaders that don't allocate a buffer of the maximum
> command line size?
>
YES! In fact, it is quite common for the command line to be dynamically
allocated.
-hpa
next prev parent reply other threads:[~2015-05-13 2:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 18:41 [PATCH] x86: Allow built-in command line to work in early kernel init Matthew Garrett
2015-04-09 20:25 ` [PATCH V2] " Matthew Garrett
2015-05-11 20:20 ` Matthew Garrett
2015-05-12 9:28 ` Ingo Molnar
2015-05-12 17:39 ` Matthew Garrett
2015-05-12 18:42 ` Matthew Garrett
2015-05-12 23:41 ` Yinghai Lu
2015-05-12 23:53 ` Matthew Garrett
2015-05-13 2:46 ` H. Peter Anvin [this message]
2015-05-13 3:06 ` Matthew Garrett
-- strict thread matches above, loose matches on Subject: below --
2015-05-19 23:09 Matthew Garrett
2015-05-20 7:42 ` Ingo Molnar
2015-05-27 23:33 ` Matthew Garrett
2015-06-03 9:24 ` Ingo Molnar
2015-06-03 16:08 ` Matthew Garrett
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=5552BAF3.7040605@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew.garrett@coreos.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=mjg59@coreos.com \
--cc=mjg59@srcf.ucam.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yinghai@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