From: patchwork-bot+netdevbpf@kernel.org
To: Alan Maguire <alan.maguire@oracle.com>
Cc: andrii@kernel.org, ast@kernel.org, jolsa@kernel.org,
acme@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
song@kernel.org, yhs@fb.com, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@google.com, haoluo@google.com,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf] libbpf: btf dedup identical struct test needs check for nested structs/arrays
Date: Tue, 25 Oct 2022 23:30:17 +0000 [thread overview]
Message-ID: <166674061767.7170.11544796321523992153.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1666622309-22289-1-git-send-email-alan.maguire@oracle.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 24 Oct 2022 15:38:29 +0100 you wrote:
> When examining module BTF, it is common to see core kernel structures
> such as sk_buff, net_device duplicated in the module. After adding
> debug messaging to BTF it turned out that much of the problem
> was down to the identical struct test failing during deduplication;
> sometimes the compiler adds identical structs. However
> it turns out sometimes that type ids of identical struct members
> can also differ, even when the containing structs are still identical.
>
> [...]
Here is the summary with links:
- [bpf] libbpf: btf dedup identical struct test needs check for nested structs/arrays
https://git.kernel.org/bpf/bpf-next/c/f3c51fe02c55
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:[~2022-10-25 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 14:38 [PATCH bpf] libbpf: btf dedup identical struct test needs check for nested structs/arrays Alan Maguire
2022-10-25 23: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=166674061767.7170.11544796321523992153.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@google.com \
--cc=song@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.