From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@ci.codeaurora.org
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
jbenc@redhat.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] libbpf: properly ignore STT_SECTION symbols in legacy map definitions
Date: Wed, 29 Sep 2021 23:00:07 +0000 [thread overview]
Message-ID: <163295640745.26180.7434864795119924642.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210929213837.832449-1-toke@redhat.com>
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Wed, 29 Sep 2021 23:38:37 +0200 you wrote:
> The previous patch to ignore STT_SECTION symbols only added the ignore
> condition in one of them. This fails if there's more than one map
> definition in the 'maps' section, because the subsequent modulus check will
> fail, resulting in error messages like:
>
> libbpf: elf: unable to determine legacy map definition size in ./xdpdump_xdp.o
>
> [...]
Here is the summary with links:
- [bpf-next] libbpf: properly ignore STT_SECTION symbols in legacy map definitions
https://git.kernel.org/bpf/bpf-next/c/161ecd537948
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-09-29 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 21:38 [PATCH bpf-next] libbpf: properly ignore STT_SECTION symbols in legacy map definitions Toke Høiland-Jørgensen
2021-09-29 23:00 ` 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=163295640745.26180.7434864795119924642.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?b?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2VuIDx0b2tlQHJlZGhhdC5jb20+?=@ci.codeaurora.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jbenc@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).