From: Thomas Gleixner <tglx@linutronix.de>
To: mingo@redhat.com, "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
"Pan, Jacob jun" <jacob.jun.pan@intel.com>
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/mrst] x86: Initialize stack canary in secondary start
Date: Sat, 20 Feb 2010 09:04:30 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1002200903170.2811@localhost.localdomain> (raw)
In-Reply-To: <tip-35f720c5930f689647d51ad77e2a8d6f0abf66c8@git.kernel.org>
On Sat, 20 Feb 2010, tip-bot for Jacob Pan wrote:
> Commit-ID: 35f720c5930f689647d51ad77e2a8d6f0abf66c8
> Gitweb: http://git.kernel.org/tip/35f720c5930f689647d51ad77e2a8d6f0abf66c8
> Author: Jacob Pan <jacob.jun.pan@intel.com>
> AuthorDate: Thu, 17 Sep 2009 07:36:43 -0700
> Committer: H. Peter Anvin <hpa@zytor.com>
> CommitDate: Fri, 19 Feb 2010 16:25:17 -0800
>
> x86: Initialize stack canary in secondary start
>
> Some secondary clockevent setup code needs to call request_irq, which
> will cause fake stack check failure in schedule() if voluntary
> preemption model is chosen. It is safe to have stack canary
> initialized here early, since start_secondary() does not return.
So with that patch applied we can remove the boot_init_stack_canary()
in process_32/64.c cpu_idle(), can't we ?
Thanks,
tglx
> Signed-off-by: Jacob Pan <jacob.jun.pan@intel.com>
> LKML-Reference: <43F901BD926A4E43B106BF17856F07559FB80D02@orsmsx508.amr.corp.intel.com>
> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
> ---
> arch/x86/kernel/smpboot.c | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
> index b4e870c..3e6150d 100644
> --- a/arch/x86/kernel/smpboot.c
> +++ b/arch/x86/kernel/smpboot.c
> @@ -48,6 +48,7 @@
> #include <linux/err.h>
> #include <linux/nmi.h>
> #include <linux/tboot.h>
> +#include <linux/stackprotector.h>
>
> #include <asm/acpi.h>
> #include <asm/desc.h>
> @@ -324,6 +325,9 @@ notrace static void __cpuinit start_secondary(void *unused)
> /* enable local interrupts */
> local_irq_enable();
>
> + /* to prevent fake stack check failure in clock setup */
> + boot_init_stack_canary();
> +
> x86_cpuinit.setup_percpu_clockev();
>
> wmb();
>
next prev parent reply other threads:[~2010-02-20 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-13 1:40 [PATCH 6/9] x86: initialize " Pan, Jacob jun
2010-02-20 1:28 ` [tip:x86/mrst] x86: Initialize " tip-bot for Jacob Pan
2010-02-20 8:04 ` Thomas Gleixner [this message]
2010-02-22 18:24 ` Pan, Jacob jun
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=alpine.LFD.2.00.1002200903170.2811@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.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
Powered by JetHome