From: Vivek Goyal <vgoyal@redhat.com>
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Neil Horman <nhorman@redhat.com>,
kexec@lists.infradead.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Kexec command line length
Date: Mon, 28 Jan 2008 16:09:17 -0500 [thread overview]
Message-ID: <20080128210917.GF32765@redhat.com> (raw)
In-Reply-To: <20080128205324.GC1174@hmsreliant.think-freely.org>
On Mon, Jan 28, 2008 at 03:53:24PM -0500, Neil Horman wrote:
> On Mon, Jan 28, 2008 at 03:20:41PM -0500, Vivek Goyal wrote:
> > >
> > > struct x86_linux_header {
> > > @@ -206,7 +210,10 @@ struct x86_linux_header {
> > > #else
> > > uint32_t kernel_alignment; /* 0x230 */
> > > uint8_t relocatable_kernel; /* 0x234 */
> > > - uint8_t tail[32*1024 - 0x235]; /* 0x230 */
> > > + uint32_t cmdline_size; /* 0x235 */
> > > + uint32_t hardware_subarch; /* 0x239 */
> > > + uint64_t hardware_subarch_data; /* 0x23D */
> >
> > We need a padding of 3 bytes here too between relocatable kernel and
> > cmdline_size, in the same way as x86_linux_param_header?
> >
>
> Oh, good catch, yes we do need that. I expect it passed my testing because the
> garbage that wound up in cmdline_size was big enough to pass the check in
> do_bzImage_load.
>
> New patch, same summary as before, with the above correction
>
> Regards
> Neil
>
> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
>
>
Thanks. Looks good to me.
Regards
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2008-01-28 21:09 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 [this message]
2008-01-28 21:29 ` Bernhard Walle
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=20080128210917.GF32765@redhat.com \
--to=vgoyal@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=nhorman@redhat.com \
--cc=nhorman@tuxdriver.com \
/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