BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next] libbpf: improve BTF dedup handling of "identical" BTF types
Date: Mon, 05 May 2025 22:00:27 +0000	[thread overview]
Message-ID: <174648242775.901475.6361056701698459458.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250501235231.1339822-1-andrii@kernel.org>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Thu,  1 May 2025 16:52:31 -0700 you wrote:
> BTF dedup has a strong assumption that compiler with deduplicate identical
> types within any given compilation unit (i.e., .c file). This property
> is used when establishing equilvalence of two subgraphs of types.
> 
> Unfortunately, this property doesn't always holds in practice. We've
> seen cases of having truly identical structs, unions, array definitions,
> and, most recently, even pointers to the same type being duplicated
> within CU.
> 
> [...]

Here is the summary with links:
  - [bpf-next] libbpf: improve BTF dedup handling of "identical" BTF types
    https://git.kernel.org/bpf/bpf-next/c/62e23f183839

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-05-05 21:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-01 23:52 [PATCH bpf-next] libbpf: improve BTF dedup handling of "identical" BTF types Andrii Nakryiko
2025-05-01 23:57 ` Andrii Nakryiko
2025-05-02  9:31 ` Alan Maguire
2025-05-02 18:09   ` Alexei Starovoitov
2025-05-05 21:10     ` Andrii Nakryiko
2025-05-05 21:53       ` Alexei Starovoitov
2025-05-06 10:15       ` Alan Maguire
2025-05-06 21:43         ` Andrii Nakryiko
2025-05-05 22: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=174648242775.901475.6361056701698459458.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=daniel@iogearbox.net \
    --cc=kernel-team@meta.com \
    --cc=martin.lau@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