From: "Arnd Bergmann" <arnd@arndb.de>
To: "Ard Biesheuvel" <ardb+git@google.com>, linux-kernel@vger.kernel.org
Cc: "Ard Biesheuvel" <ardb@kernel.org>,
"Masahiro Yamada" <masahiroy@kernel.org>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
Linux-Arch <linux-arch@vger.kernel.org>,
linux-kbuild@vger.kernel.org, bpf@vger.kernel.org,
"Andrii Nakryiko" <andrii@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Kees Cook" <keescook@chromium.org>
Subject: Re: [PATCH v2 1/3] kallsyms: Avoid weak references for kallsyms symbols
Date: Tue, 09 Apr 2024 17:04:36 +0200 [thread overview]
Message-ID: <b60ba66d-4028-4fc1-89be-41889768990b@app.fastmail.com> (raw)
In-Reply-To: <20240409150132.4097042-6-ardb+git@google.com>
On Tue, Apr 9, 2024, at 17:01, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@kernel.org>
>
> 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.
>
> Tested-by: Nick Desaulniers <ndesaulniers@google.com> # Boot
> Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>
> Reviewed-by: Kees Cook <keescook@chromium.org>
> Link: https://lkml.kernel.org/r/20230504174320.3930345-1-ardb%40kernel.org
> Signed-off-by: Ard Biesheuvel <ardb@kernel.org>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2024-04-09 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 15:01 [PATCH v2 0/3] kbuild: Avoid weak external linkage where possible Ard Biesheuvel
2024-04-09 15:01 ` [PATCH v2 1/3] kallsyms: Avoid weak references for kallsyms symbols Ard Biesheuvel
2024-04-09 15:04 ` Arnd Bergmann [this message]
2024-04-09 15:01 ` [PATCH v2 2/3] vmlinux: Avoid weak reference to notes section Ard Biesheuvel
2024-04-09 15:04 ` Arnd Bergmann
2024-04-09 15:01 ` [PATCH v2 3/3] btf: Avoid weak external references Ard Biesheuvel
2024-04-09 15:05 ` Arnd Bergmann
2024-04-10 8:21 ` Jiri Olsa
2024-04-10 8:37 ` Ard Biesheuvel
2024-04-10 9:30 ` Jiri Olsa
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=b60ba66d-4028-4fc1-89be-41889768990b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andrii@kernel.org \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=masahiroy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox