linux-kernel - Re: [PATCH v2 3/3] btf: Avoid weak external references

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date: Tue, 09 Apr 2024 17:05:08 +0200
From: "Arnd Bergmann" <arnd@...db.de>
To: "Ard Biesheuvel" <ardb+git@...gle.com>, linux-kernel@...r.kernel.org
Cc: "Ard Biesheuvel" <ardb@...nel.org>,
 "Masahiro Yamada" <masahiroy@...nel.org>,
 "Martin KaFai Lau" <martin.lau@...ux.dev>,
 Linux-Arch <linux-arch@...r.kernel.org>, linux-kbuild@...r.kernel.org,
 bpf@...r.kernel.org, "Andrii Nakryiko" <andrii@...nel.org>
Subject: Re: [PATCH v2 3/3] btf: Avoid weak external references

On Tue, Apr 9, 2024, at 17:01, Ard Biesheuvel wrote:
> From: Ard Biesheuvel <ardb@...nel.org>
>
> If the BTF code is enabled in the build configuration, the start/stop
> BTF markers are guaranteed to exist in the final link but not during the
> first linker pass.
>
> Avoid GOT based relocations to these markers in the final executable by
> providing preliminary definitions that will be used by the first linker
> pass, and superseded by the actual definitions in the subsequent ones.
>
> Make the preliminary definitions dependent on CONFIG_DEBUG_INFO_BTF so
> that inadvertent references to this section will trigger a link failure
> if they occur in code that does not honour CONFIG_DEBUG_INFO_BTF.
>
> Note that Clang will notice that taking the address of__start_BTF cannot
> yield NULL any longer, so testing for that condition is no longer
> needed.
>
> Acked-by: Andrii Nakryiko <andrii@...nel.org>
> Signed-off-by: Ard Biesheuvel <ardb@...nel.org>

Acked-by: Arnd Bergmann <arnd@...db.de>