From: Rusty Russell <rusty@rustcorp.com.au>
To: linux-ia64@vger.kernel.org
Subject: Re: [patch 10/20] kallsyms: fix absolute addresses for kASLR
Date: Tue, 11 Mar 2014 00:48:08 +0000 [thread overview]
Message-ID: <87k3c1y3k7.fsf@rustcorp.com.au> (raw)
In-Reply-To: <87k3c8yr9u.fsf@rustcorp.com.au>
Kees Cook <keescook@chromium.org> writes:
> On Thu, Mar 6, 2014 at 7:20 PM, Rusty Russell <rusty@rustcorp.com.au> wrote:
>> What is "the x86 relocs tool"?
>
> arch/x86/tools/relocs.c is used to generate relocation information on
> x86-32 (always) and x86-64 (under kASLR). It deals with all kinds of
> weird special cases that various linkers do differently. I'm glad I
> didn't have to touch this code again. :)
Well, let's fix it!
Making these symbols absolute seems like the Right Thing. We can work
around it for the moment but I'll look at that once we have a minimal
fix for now (see other thread).
Thanks,
Rusty.
prev parent reply other threads:[~2014-03-11 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 2:57 [patch 10/20] kallsyms: fix absolute addresses for kASLR Rusty Russell
2014-03-06 19:15 ` Kees Cook
2014-03-06 21:25 ` Kees Cook
2014-03-07 0:34 ` Kees Cook
2014-03-07 3:32 ` Rusty Russell
2014-03-07 5:37 ` Kees Cook
2014-03-11 0:48 ` Rusty Russell [this message]
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=87k3c1y3k7.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-ia64@vger.kernel.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