From: Ingo Molnar <mingo@elte.hu>
To: James Morris <jmorris@namei.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Regression [Was: Boot hang with stack protector on x86_64]
Date: Fri, 22 Feb 2008 13:17:51 +0100 [thread overview]
Message-ID: <20080222121751.GA17889@elte.hu> (raw)
In-Reply-To: <Xine.LNX.4.64.0802222133150.6937@us.intercode.com.au>
* James Morris <jmorris@namei.org> wrote:
> > works fine for you? That has all the current stackprotector fixes. I
> > plan to send a separate pull request with just the stackprotector
> > fixes to Linus, they are looking good in testing so far.
>
> Nope, same problem.
>
> (I followed your instructions in the readme exactly).
stupid double check, does "git-log | grep stackpro" give you the fixes:
This patch adds a simple self-test capability to the stackprotector
x86: unify stackprotector features
streamline the stackprotector features under a single option
x86: stackprotector: mix TSC to the boot canary
x86: fix the stackprotector canary of the boot CPU
stackprotector: add boot_init_stack_canary()
stackprotector: include files
?
Please send me your full .config and the gcc version you used for
building the failing kernel.
Ingo
next prev parent reply other threads:[~2008-02-22 12:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 0:29 Boot hang with stack protector on x86_64 James Morris
2008-02-22 1:14 ` Arjan van de Ven
2008-02-22 7:59 ` Regression [Was: Boot hang with stack protector on x86_64] Sam Ravnborg
2008-02-22 9:36 ` Ingo Molnar
2008-02-22 10:33 ` James Morris
2008-02-22 12:17 ` Ingo Molnar [this message]
2008-02-22 13:02 ` James Morris
2008-02-22 13:27 ` Ingo Molnar
2008-02-23 6:18 ` Ingo Molnar
2008-02-23 7:37 ` Ingo Molnar
2008-02-24 22:53 ` James Morris
2008-02-25 8:23 ` Ingo Molnar
2008-02-22 15:43 ` Linus Torvalds
2008-02-22 15:59 ` Arjan van de Ven
2008-02-22 16:12 ` Sam Ravnborg
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=20080222121751.GA17889@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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