From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757957AbYHGNQ5 (ORCPT ); Thu, 7 Aug 2008 09:16:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751971AbYHGNQq (ORCPT ); Thu, 7 Aug 2008 09:16:46 -0400 Received: from mx1.redhat.com ([66.187.233.31]:44127 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751515AbYHGNQp (ORCPT ); Thu, 7 Aug 2008 09:16:45 -0400 Date: Thu, 7 Aug 2008 09:15:57 -0400 From: Vivek Goyal To: Huang Ying Cc: "Eric W. Biederman" , Pavel Machek , nigel@nigel.suspend2.net, "Rafael J. Wysocki" , Andrew Morton , mingo@elte.hu, Linus Torvalds , linux-kernel@vger.kernel.org, Kexec Mailing List Subject: Re: [PATCH 2/6] kexec jump: check code size in control page Message-ID: <20080807131557.GB27783@redhat.com> References: <1218099926.5164.33.camel@caritas-dev.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1218099926.5164.33.camel@caritas-dev.intel.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 07, 2008 at 05:05:26PM +0800, Huang Ying wrote: > Kexec/Kexec-jump requires code size in control page is less than > PAGE_SIZE/2. This patch adds runtime checking for this. > > Signed-off-by: Huang Ying > > --- > arch/x86/kernel/machine_kexec_32.c | 4 ++++ > arch/x86/kernel/relocate_kernel_32.S | 3 +++ > include/asm-x86/kexec.h | 1 + > 3 files changed, 8 insertions(+) > > --- a/arch/x86/kernel/machine_kexec_32.c > +++ b/arch/x86/kernel/machine_kexec_32.c > @@ -92,6 +92,10 @@ int machine_kexec_prepare(struct kimage > { > 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); > + Hi Huang, 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. Thanks Vivek