BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mingpei CAO <caomingpei@gmail.com>
Cc: bpf@vger.kernel.org, alexei.starovoitov@gmail.com,
	andrii@kernel.org, eddyz87@gmail.com, alan.maguire@oracle.com
Subject: Re: [PATCH bpf v2 0/2] libbpf: Fix array comparison in BTF dedup
Date: Tue, 08 Sep 2026 23:40:05 +0000	[thread overview]
Message-ID: <178891080539.64512.8091983797473568785.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260908164920.108074-1-caomingpei@gmail.com>

Hello:

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

On Tue,  8 Sep 2026 16:49:18 +0000 you wrote:
> The recursive array comparison in BTF dedup reads both descriptors from
> the first type. This can merge distinct structures and corrupt CO-RE
> relocation metadata. Fix the comparison and add three regression cases to
> the existing BTF dedup tests.
> 
> Changes in v2:
> - Move the tests into prog_tests/btf.c using Alan Maguire's two cases.
> - Add a separate negative case with the same index type to isolate
>   element-type comparison.
> - Keep patch 1 unchanged.
> 
> [...]

Here is the summary with links:
  - [bpf,v2,1/2] libbpf: Fix array comparison in BTF dedup
    https://git.kernel.org/bpf/bpf-next/c/e62c5b97d6c4
  - [bpf,v2,2/2] selftests/bpf: Test array element comparison in BTF dedup
    https://git.kernel.org/bpf/bpf-next/c/208637af0dc2

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



      parent reply	other threads:[~2026-09-08 23:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 16:49 [PATCH bpf v2 0/2] libbpf: Fix array comparison in BTF dedup Mingpei CAO
2026-09-08 16:49 ` [PATCH bpf v2 1/2] " Mingpei CAO
2026-09-08 17:01   ` sashiko-bot
2026-09-08 16:49 ` [PATCH bpf v2 2/2] selftests/bpf: Test array element " Mingpei CAO
2026-09-08 23:40 ` 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=178891080539.64512.8091983797473568785.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alan.maguire@oracle.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=caomingpei@gmail.com \
    --cc=eddyz87@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