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: Wed, 16 Oct 2013 08:56:30 +0200 [thread overview]
Message-ID: <20131016065630.GC22509@gmail.com> (raw)
In-Reply-To: <CAGXu5jL2sK86PeEiumJ-4bWQeCYg9BzEBAVOhQeNnHAC2ZPSYA@mail.gmail.com>
* Kees Cook <keescook@chromium.org> wrote:
> >> > 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)
> >>
> >> Can you try with the gold linker? When not using Gold, I can produce
> >> a similar crash with GNU ld ver 2.23.2 but not 2.22.
> >
> > I'm not set up for Gold - but maybe others can try your experiment.
> >
> > If you can see/reproduce the 2.23 crash then maybe that fix will work
> > for my testcase as well.
>
> I haven't isolated the problem with 2.23 yet, but I'll start digging.
I've excluded tip:x86/kaslr from tip:master meanwhile.
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-16 6:56 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
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 [this message]
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=20131016065630.GC22509@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.