From: Rusty Russell <rusty@rustcorp.com.au>
To: Kees Cook <keescook@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andrew Honig <ahonig@google.com>, Michal Marek <mmarek@suse.cz>,
"x86@kernel.org" <x86@kernel.org>, Tejun Heo <tj@kernel.org>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] kallsyms: handle special absolute symbols
Date: Thu, 13 Mar 2014 03:52:35 +0000 [thread overview]
Message-ID: <87lhwevk98.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAGXu5j+Zto=D_UYgn6DLVcOQyB_8sAs86masY8iuDTU5ZEZ8OQ@mail.gmail.com>
Kees Cook <keescook@chromium.org> writes:
> Why not just do this with 0-base-address detection like my v2? That
> would mean we don't need to remember to add this flag in the future to
> imagined new architectures that might want this 0-based per_cpu
> feature.
Because future architectures will get this right and emit absolute
symbols. I hope!
I'm swamped at the moment, but am hoping to investigate that for
x86-64. This is a stop-gap.
Cheers,
Rusty.
WARNING: multiple messages have this Message-ID (diff)
From: Rusty Russell <rusty@rustcorp.com.au>
To: Kees Cook <keescook@chromium.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andrew Honig <ahonig@google.com>, Michal Marek <mmarek@suse.cz>,
"x86\@kernel.org" <x86@kernel.org>, Tejun Heo <tj@kernel.org>,
Tony Luck <tony.luck@intel.com>,
Fenghua Yu <fenghua.yu@intel.com>,
linux-ia64@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] kallsyms: handle special absolute symbols
Date: Thu, 13 Mar 2014 14:10:35 +1030 [thread overview]
Message-ID: <87lhwevk98.fsf@rustcorp.com.au> (raw)
In-Reply-To: <CAGXu5j+Zto=D_UYgn6DLVcOQyB_8sAs86masY8iuDTU5ZEZ8OQ@mail.gmail.com>
Kees Cook <keescook@chromium.org> writes:
> Why not just do this with 0-base-address detection like my v2? That
> would mean we don't need to remember to add this flag in the future to
> imagined new architectures that might want this 0-based per_cpu
> feature.
Because future architectures will get this right and emit absolute
symbols. I hope!
I'm swamped at the moment, but am hoping to investigate that for
x86-64. This is a stop-gap.
Cheers,
Rusty.
next prev parent reply other threads:[~2014-03-13 3:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 1:00 [PATCH v2 0/2] kallsyms: handle special absolute symbols Kees Cook
2014-03-08 1:00 ` Kees Cook
2014-03-08 1:00 ` [PATCH v2 1/2] kallsyms: generalize address range checking Kees Cook
2014-03-08 1:00 ` Kees Cook
2014-03-08 1:00 ` [PATCH v2 2/2] kallsyms: handle special absolute symbols Kees Cook
2014-03-08 1:00 ` Kees Cook
2014-03-11 21:03 ` Kees Cook
2014-03-11 21:03 ` Kees Cook
2014-03-13 0:30 ` Rusty Russell
2014-03-13 0:42 ` Rusty Russell
2014-03-13 0:40 ` Kees Cook
2014-03-13 0:40 ` Kees Cook
2014-03-13 3:40 ` Rusty Russell [this message]
2014-03-13 3:52 ` Rusty Russell
2014-03-13 6:23 ` Kees Cook
2014-03-13 6:23 ` Kees Cook
2014-03-17 3:36 ` Rusty Russell
2014-03-17 3:48 ` Rusty Russell
2014-03-10 19:06 ` [PATCH v2 0/2] " Andrew Morton
2014-03-10 19:06 ` Andrew Morton
2014-03-10 19:58 ` Kees Cook
2014-03-10 19:58 ` Kees Cook
2014-03-10 20:02 ` Andrew Morton
2014-03-10 20:02 ` Andrew Morton
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=87lhwevk98.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=ahonig@google.com \
--cc=akpm@linux-foundation.org \
--cc=fenghua.yu@intel.com \
--cc=keescook@chromium.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=tj@kernel.org \
--cc=tony.luck@intel.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 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.