From: Ingo Molnar <mingo@kernel.org>
To: Kees Cook <keescook@chromium.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>,
Michael Davidson <md@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@linux.intel.com>,
"linux-tip-commits@vger.kernel.org"
<linux-tip-commits@vger.kernel.org>
Subject: Re: [tip:x86/kaslr] x86, relocs: Add more per-cpu gold special cases
Date: Tue, 15 Oct 2013 08:04:25 +0200 [thread overview]
Message-ID: <20131015060425.GB3866@gmail.com> (raw)
In-Reply-To: <CAGXu5j+tQfUpmem85WK5-ootoJM1mCH6BPDr3pfR2sHwoFy_8A@mail.gmail.com>
* Kees Cook <keescook@chromium.org> wrote:
> On Mon, Oct 14, 2013 at 9:28 AM, H. Peter Anvin <hpa@zytor.com> wrote:
> > On 10/14/2013 07:19 AM, H. Peter Anvin wrote:
> >> My guess is that the 95 addresses are randomized and the 82 address is an address which failed to relocate.
> >
> >> ffffffff82a04a58 is:
> >> ffffffff82a03000 t init_per_cpu__gdt_page
> >
> >
> > Specifically, it looks like the percpu stuff isn't getting set up correctly.
>
> It wouldn't surprise me if there are even more percpu things to fix.
> It's the main area we've continued to trip over while working on this
> with various linkers. Which linker and version are you seeing this
> with?
The failure I saw triggered with fairly modern userspace:
GNU ld version 2.23.52.0.1-9.fc19 20130226
gcc version 4.8.1 20130603 (Red Hat 4.8.1-1) (GCC)
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-15 6:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 1:39 [PATCH v2] x86, relocs: add more per-cpu gold special cases Kees Cook
2013-10-13 12:01 ` [tip:x86/kaslr] x86, relocs: Add " tip-bot for Michael Davidson
2013-10-14 8:30 ` Ingo Molnar
2013-10-14 9:38 ` Ingo Molnar
2013-10-14 14:19 ` H. Peter Anvin
2013-10-14 16:28 ` H. Peter Anvin
2013-10-14 20:47 ` Kees Cook
2013-10-15 6:04 ` Ingo Molnar [this message]
2013-10-15 15:42 ` Kees Cook
2013-10-15 16:03 ` Ingo Molnar
2013-10-15 17:22 ` Kees Cook
2013-10-16 6:56 ` Ingo Molnar
2013-10-16 14:53 ` Kees Cook
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=20131015060425.GB3866@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=md@google.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.