public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ard Biesheuvel <ardb+git@google.com>
Cc: linux-kernel@vger.kernel.org, ardb@kernel.org,
	masahiroy@kernel.org, arnd@arndb.de, martin.lau@linux.dev,
	linux-arch@vger.kernel.org, linux-kbuild@vger.kernel.org,
	bpf@vger.kernel.org, andrii@kernel.org, olsajiri@gmail.com
Subject: Re: [PATCH v4 0/3] kbuild: Avoid weak external linkage where possible
Date: Tue, 16 Apr 2024 14:40:27 +0000	[thread overview]
Message-ID: <171327842741.29461.3030265084386428643.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240415162041.2491523-5-ardb+git@google.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Mon, 15 Apr 2024 18:20:42 +0200 you wrote:
> From: Ard Biesheuvel <ardb@kernel.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



  parent reply	other threads:[~2024-04-16 14:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15 16:20 [PATCH v4 0/3] kbuild: Avoid weak external linkage where possible Ard Biesheuvel
2024-04-15 16:20 ` [PATCH v4 1/3] kallsyms: Avoid weak references for kallsyms symbols Ard Biesheuvel
2024-04-23 13:44   ` Masahiro Yamada
2024-04-15 16:20 ` [PATCH v4 2/3] vmlinux: Avoid weak reference to notes section Ard Biesheuvel
2024-04-20 13:42   ` Masahiro Yamada
2024-04-15 16:20 ` [PATCH v4 3/3] btf: Avoid weak external references Ard Biesheuvel
2024-04-16 14:40 ` patchwork-bot+netdevbpf [this message]
2024-04-19  7:57   ` [PATCH v4 0/3] kbuild: Avoid weak external linkage where possible Ard Biesheuvel
2024-04-20 12:31     ` Masahiro Yamada
2024-04-20 12:35       ` Ard Biesheuvel
2024-04-20 13:41         ` Masahiro Yamada
2024-04-20 13:56           ` Ard Biesheuvel
2024-04-20 13:59             ` Ard Biesheuvel
2024-04-20 14:05               ` Masahiro Yamada

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=171327842741.29461.3030265084386428643.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ardb+git@google.com \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=bpf@vger.kernel.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=olsajiri@gmail.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