From: Kees Cook <keescook@chromium.org>
To: Ard Biesheuvel <ardb@kernel.org>
Cc: linux-arch@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Fangrui Song <maskray@google.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: Re: [RFC PATCH] kallsyms: Avoid weak references for kallsyms symbols
Date: Tue, 16 May 2023 12:50:49 -0700 [thread overview]
Message-ID: <202305161248.F0B3D1D@keescook> (raw)
In-Reply-To: <20230504174320.3930345-1-ardb@kernel.org>
On Thu, May 04, 2023 at 07:43:20PM +0200, Ard Biesheuvel wrote:
> kallsyms is a directory of all the symbols in the vmlinux binary, and so
> creating it is somewhat of a chicken-and-egg problem, as its non-zero
> size affects the layout of the binary, and therefore the values of the
> symbols.
>
> For this reason, the kernel is linked more than once, and the first pass
> does not include any kallsyms data at all. For the linker to accept
> this, the symbol declarations describing the kallsyms metadata are
> emitted as having weak linkage, so they can remain unsatisfied. During
> the subsequent passes, the weak references are satisfied by the kallsyms
> metadata that was constructed based on information gathered from the
> preceding passes.
>
> Weak references lead to somewhat worse codegen, because taking their
> address may need to produce NULL (if the reference was unsatisfied), and
> this is not usually supported by RIP or PC relative symbol references.
>
> Given that these references are ultimately always satisfied in the final
> link, let's drop the weak annotation, and instead, provide fallback
> definitions in the linker script that are only emitted if an unsatisfied
> reference exists.
>
> While at it, drop the FRV specific annotation that these symbols reside
> in .rodata - FRV is long gone.
>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Fangrui Song <maskray@google.com>
> Cc: Nathan Chancellor <nathan@kernel.org>
> Cc: Nick Desaulniers <ndesaulniers@google.com>
> Cc: Kees Cook <keescook@chromium.org>
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
> ---
> include/asm-generic/vmlinux.lds.h | 9 +++++++
> kernel/kallsyms.c | 6 -----
> kernel/kallsyms_internal.h | 25 +++++++-------------
> 3 files changed, 18 insertions(+), 22 deletions(-)
>
> diff --git a/include/asm-generic/vmlinux.lds.h b/include/asm-generic/vmlinux.lds.h
> index d1f57e4868ed341d..dd42c0fcad2b519f 100644
> --- a/include/asm-generic/vmlinux.lds.h
> +++ b/include/asm-generic/vmlinux.lds.h
> @@ -460,6 +460,15 @@
> */
> #define RO_DATA(align) \
> . = ALIGN((align)); \
> + PROVIDE(kallsyms_addresses = .); \
> + PROVIDE(kallsyms_offsets = .); \
> + PROVIDE(kallsyms_names = .); \
> + PROVIDE(kallsyms_num_syms = .); \
> + PROVIDE(kallsyms_relative_base = .); \
> + PROVIDE(kallsyms_token_table = .); \
> + PROVIDE(kallsyms_token_index = .); \
> + PROVIDE(kallsyms_markers = .); \
> + PROVIDE(kallsyms_seqs_of_names = .); \
Perhaps add comments here and in kernel/kallsyms_internal.h to correlate
this list and the externs? "This list is needed because ..., see the
externs in kallsyms_internal.h." or similar?
Otherwise, yeah, looks good.
Reviewed-by: Kees Cook <keescook@chromium.org>
--
Kees Cook
prev parent reply other threads:[~2023-05-16 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 17:43 [RFC PATCH] kallsyms: Avoid weak references for kallsyms symbols Ard Biesheuvel
2023-05-15 21:29 ` Nick Desaulniers
2023-05-16 17:22 ` Ard Biesheuvel
2023-05-16 19:50 ` Kees Cook [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=202305161248.F0B3D1D@keescook \
--to=keescook@chromium.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=maskray@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
/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.