From: Guenter Roeck <linux@roeck-us.net>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
keescook@chromium.org, akpm@linux-foundation.org,
mingo@kernel.org, hpa@zytor.com, heiko.carstens@de.ibm.com,
benh@kernel.crashing.org, mpe@ellerman.id.au, mmarek@suse.cz,
rusty@rustcorp.com.au, arnd@arndb.de, linux-arch@vger.kernel.org
Subject: Re: [PATCH v4 0/3] kallsyms base relative series
Date: Mon, 25 Jan 2016 09:44:10 -0800 [thread overview]
Message-ID: <56A65EEA.8010908@roeck-us.net> (raw)
In-Reply-To: <1453731572-18448-1-git-send-email-ard.biesheuvel@linaro.org>
On 01/25/2016 06:19 AM, Ard Biesheuvel wrote:
> This v4 of my kallsyms base relative implementation is now a 3 piece series,
> since it caused some problems due to the way absolute symbols are handled
> by the absolute per cpu code. As it turns out, that code was probably wrong
> in the sense that it caused non-relocated symbol addresses to be emitted
> for values that are in fact relative to the address of the kernel text.
>
> Patch #1 fixes the scripts/kallsyms invocation to only pass the x86_64
> specific --absolute-percpu option if CONFIG_SMP is also set.
>
> Patch #2 reworks the absolute percpu code to only emit those percpu symbols
> as absolute, and not symbols that have been classified as 'A' (absolute) by
> the linker, since that does not mean quite the same thing.
>
> Patch #3 is the original kallsyms base relative patch, with some
> modifications:
> - folded the s/ULLONG_MAX/-1ULL? change made by Andrew
> - ensured that the kallsyms_relative_base value itself is relocated as
> required.
> - dropped all of the acks and other tags, as they have become outdated with
> the recent changes to this patch.
>
I tested the series on top of mmotm (after reverting the original patches).
Qemu tests for mips, sparc, and x86 (both smp and nosmp) now pass.
Tested-by: Guenter Roeck <linux@roeck-us.net>
> Ard Biesheuvel (3):
> x86: kallsyms: disable absolute percpu symbols on !SMP
> kallsyms: don't overload absolute symbol type for percpu symbols
> kallsyms: add support for relative offsets in kallsyms address table
>
> init/Kconfig | 16 +++
> kernel/kallsyms.c | 38 ++++++--
> scripts/kallsyms.c | 102 +++++++++++++++++---
> scripts/link-vmlinux.sh | 6 +-
> scripts/namespace.pl | 2 +
> 5 files changed, 142 insertions(+), 22 deletions(-)
>
next prev parent reply other threads:[~2016-01-25 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 14:19 [PATCH v4 0/3] kallsyms base relative series Ard Biesheuvel
2016-01-25 14:19 ` [PATCH v4 1/3] x86: kallsyms: disable absolute percpu symbols on !SMP Ard Biesheuvel
2016-01-25 14:19 ` [PATCH v4 2/3] kallsyms: don't overload absolute symbol type for percpu symbols Ard Biesheuvel
2016-01-25 14:19 ` [PATCH v4 3/3] kallsyms: add support for relative offsets in kallsyms address table Ard Biesheuvel
2016-01-25 14:19 ` Ard Biesheuvel
2016-01-25 17:44 ` Guenter Roeck [this message]
2016-01-25 18:53 ` [PATCH v4 0/3] kallsyms base relative series Kees Cook
2016-01-25 18: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=56A65EEA.8010908@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=heiko.carstens@de.ibm.com \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=mmarek@suse.cz \
--cc=mpe@ellerman.id.au \
--cc=rusty@rustcorp.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).