From: Vivek Goyal <vgoyal@redhat.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Pavel Machek <pavel@suse.cz>,
"Eric W. Biederman" <ebiederm@xmission.com>,
nigel@nigel.suspend2.net, "Rafael J. Wysocki" <rjw@sisk.pl>,
Andrew Morton <akpm@linux-foundation.org>,
mingo@elte.hu, Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Kexec Mailing List <kexec@lists.infradead.org>
Subject: Re: [PATCH 2/6] kexec jump: check code size in control page
Date: Fri, 8 Aug 2008 09:52:25 -0400 [thread overview]
Message-ID: <20080808135225.GD3840@redhat.com> (raw)
In-Reply-To: <1218163477.22039.10.camel@caritas-dev.intel.com>
On Fri, Aug 08, 2008 at 10:44:37AM +0800, Huang Ying wrote:
> On Thu, 2008-08-07 at 22:31 +0200, Pavel Machek wrote:
> > Hi!
> >
> > > > PAGE_SIZE/2. This patch adds runtime checking for this.
> > > >
> > > > Signed-off-by: Huang Ying <ying.huang@intel.com>
> > ...
> >
> > > > {
> > > > if (nx_enabled)
> > > > set_pages_x(image->control_code_page, 1);
> > > > +
> > > > + BUG_ON((unsigned long)kexec_control_page_code_end - \
> > > > + (unsigned long)relocate_kernel >= PAGE_SIZE/2);
> > > > +
> > >
> >
> > > Run time check is better than nothing but I think in this case it would
> > > be better if we can catch it at compile time.
> > >
> > > One of the methods will be to write a small program of your own and
> > > put in script/ and at build time check for the size and flag error. May
> > > be there are other better ways to do this.
> >
> > BUILD_BUG_ON()?
>
> I tried with BUILD_BUG_ON(), and compiling is OK for both of following
> statement:
>
> BUILD_BUG_ON((unsigned long)kexec_control_page_code_end - \
> (unsigned long)relocate_kernel >= PAGE_SIZE/2);
>
> BUILD_BUG_ON((unsigned long)kexec_control_page_code_end - \
> (unsigned long)relocate_kernel < PAGE_SIZE/2);
>
> In general, I think value of kexec_control_page_code_end and
> relocate_kernel is not determined during compiling time. So
> BUILD_BUG_ON() doesn't work.
>
> Another idea, use ASSERT() command of ld link script as in the following
> patch:
>
> --- a/arch/x86/kernel/vmlinux_32.lds.S
> +++ b/arch/x86/kernel/vmlinux_32.lds.S
> @@ -209,3 +209,5 @@ SECTIONS
>
> DWARF_DEBUG
> }
> +
> +#include "vmlinux_check_32.lds.S"
> --- /dev/null
> +++ b/arch/x86/kernel/vmlinux_check_32.lds.S
> @@ -0,0 +1,3 @@
> +#include <asm/kexec.h>
> +
> +ASSERT(kexec_control_page_code_end - relocate_kernel >= 2048, "kexec control page code size is too big")
>
>
Use of ASSERT() looks good to me. I think creation of extra file for a
single ASSERT() can be avoided. Instead, we can just put this assert in
vmlinux_32.lds.S itself?
Thansk
Vivek
prev parent reply other threads:[~2008-08-08 13:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-07 9:05 [PATCH 2/6] kexec jump: check code size in control page Huang Ying
2008-08-07 9:21 ` Pavel Machek
2008-08-07 13:15 ` Vivek Goyal
2008-08-07 20:31 ` Pavel Machek
2008-08-08 2:44 ` Huang Ying
2008-08-08 13:52 ` Vivek Goyal [this message]
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=20080808135225.GD3840@redhat.com \
--to=vgoyal@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
--cc=ying.huang@intel.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