[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<171327842741.29461.3030265084386428643.git-patchwork-notify@kernel.org>
Date: Tue, 16 Apr 2024 14:40:27 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Ard Biesheuvel <ardb+git@...gle.com>
Cc: linux-kernel@...r.kernel.org, ardb@...nel.org, masahiroy@...nel.org,
arnd@...db.de, martin.lau@...ux.dev, linux-arch@...r.kernel.org,
linux-kbuild@...r.kernel.org, bpf@...r.kernel.org, andrii@...nel.org,
olsajiri@...il.com
Subject: Re: [PATCH v4 0/3] kbuild: Avoid weak external linkage where possible
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@...earbox.net>:
On Mon, 15 Apr 2024 18:20:42 +0200 you wrote:
> From: Ard Biesheuvel <ardb@...nel.org>
>
> Weak external linkage is intended for cases where a symbol reference
> can remain unsatisfied in the final link. Taking the address of such a
> symbol should yield NULL if the reference was not satisfied.
>
> Given that ordinary RIP or PC relative references cannot produce NULL,
> some kind of indirection is always needed in such cases, and in position
> independent code, this results in a GOT entry. In ordinary code, it is
> arch specific but amounts to the same thing.
>
> [...]
Here is the summary with links:
- [v4,1/3] kallsyms: Avoid weak references for kallsyms symbols
(no matching commit)
- [v4,2/3] vmlinux: Avoid weak reference to notes section
(no matching commit)
- [v4,3/3] btf: Avoid weak external references
https://git.kernel.org/bpf/bpf-next/c/fc5eb4a84e4c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists