From: patchwork-bot+netdevbpf@kernel.org
To: Yichong Chen <chenyichong@uniontech.com>
Cc: emil@etsalapatis.com, qmo@kernel.org, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, jolsa@kernel.org,
jiayuan.chen@linux.dev, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/2] tools/bpf/bpftool: Fix vmlinux BTF state cleanup
Date: Wed, 01 Jul 2026 18:20:22 +0000 [thread overview]
Message-ID: <178293002265.1238008.17846374226094054785.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <12A35C14DA710D2E+20260624025055.1574875-1-chenyichong@uniontech.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Wed, 24 Jun 2026 10:50:53 +0800 you wrote:
> This series fixes stale vmlinux BTF state in bpftool batch mode.
>
> Patch 1 resets the map command cached vmlinux BTF pointer when the
> command releases it, and avoids freeing the cached object from the
> map lookup path.
>
> Patch 2 resets the struct_ops command cached vmlinux BTF pointer and
> dependent cached map info state after each struct_ops command.
>
> [...]
Here is the summary with links:
- [v4,1/2] tools/bpf/bpftool: Reset vmlinux BTF after map commands
https://git.kernel.org/bpf/bpf-next/c/66d7e39e49b0
- [v4,2/2] tools/bpf/bpftool: Reset vmlinux BTF after struct_ops commands
https://git.kernel.org/bpf/bpf-next/c/f7f540e19751
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:[~2026-07-01 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-24 2:50 [PATCH v4 0/2] tools/bpf/bpftool: Fix vmlinux BTF state cleanup Yichong Chen
2026-07-01 13:10 ` Quentin Monnet
2026-07-01 18:20 ` 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=178293002265.1238008.17846374226094054785.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=chenyichong@uniontech.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=jiayuan.chen@linux.dev \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=qmo@kernel.org \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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.