BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eric Long via B4 Relay <devnull+i.hack3r.moe@kernel.org>
Cc: bpf@vger.kernel.org, andrii@kernel.org, ast@kernel.org,
	netdev@vger.kernel.org, i@hack3r.moe
Subject: Re: [PATCH bpf-next v4 0/2] BPF static linker: fix linking duplicate extern functions
Date: Tue, 08 Oct 2024 03:30:34 +0000	[thread overview]
Message-ID: <172835823448.66789.7596290486651516596.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241002-libbpf-dup-extern-funcs-v4-0-560eb460ff90@hack3r.moe>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed, 02 Oct 2024 14:25:05 +0800 you wrote:
> Currently, if `bpftool gen object` tries to link two objects that
> contains the same extern function prototype, libbpf will try to get
> their (non-existent) size by calling bpf__resolve_size like extern
> variables and fail with:
> 
> 	libbpf: global 'whatever': failed to resolve size of underlying type: -22
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,1/2] libbpf: do not resolve size on duplicate FUNCs
    https://git.kernel.org/bpf/bpf-next/c/4b146e95da87
  - [bpf-next,v4,2/2] selftests/bpf: test linking with duplicate extern functions
    https://git.kernel.org/bpf/bpf-next/c/3c591de28543

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-10-08  3:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-02  6:25 [PATCH bpf-next v4 0/2] BPF static linker: fix linking duplicate extern functions Eric Long via B4 Relay
2024-10-02  6:25 ` [PATCH bpf-next v4 1/2] libbpf: do not resolve size on duplicate FUNCs Eric Long via B4 Relay
2024-10-02  6:25 ` [PATCH bpf-next v4 2/2] selftests/bpf: test linking with duplicate extern functions Eric Long via B4 Relay
2024-10-08  3:30 ` patchwork-bot+netdevbpf [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=172835823448.66789.7596290486651516596.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=devnull+i.hack3r.moe@kernel.org \
    --cc=i@hack3r.moe \
    --cc=netdev@vger.kernel.org \
    /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