From: patchwork-bot+netdevbpf@kernel.org
To: Sami Tolvanen <samitolvanen@google.com>
Cc: bpf@vger.kernel.org, vadim.fedorenko@linux.dev, ast@kernel.org,
daniel@iogearbox.net, andrii@kernel.org, martin.lau@linux.dev,
eddyz87@gmail.com, song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, vmalik@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next v5 0/4] Use correct destructor kfunc types
Date: Tue, 13 Jan 2026 03:00:13 +0000 [thread overview]
Message-ID: <176827321329.1651449.11456880793258426338.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260110082548.113748-6-samitolvanen@google.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sat, 10 Jan 2026 08:25:49 +0000 you wrote:
> Hi folks,
>
> While running BPF self-tests with CONFIG_CFI (Control Flow
> Integrity) enabled, I ran into a couple of failures in
> bpf_obj_free_fields() caused by type mismatches between the
> btf_dtor_kfunc_t function pointer type and the registered
> destructor functions.
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/4] bpf: crypto: Use the correct destructor kfunc type
https://git.kernel.org/bpf/bpf-next/c/b40a5d724f29
- [bpf-next,v5,2/4] bpf: net_sched: Use the correct destructor kfunc type
https://git.kernel.org/bpf/bpf-next/c/c99d97b46631
- [bpf-next,v5,3/4] selftests/bpf: Use the correct destructor kfunc type
https://git.kernel.org/bpf/bpf-next/c/ba7f1024a102
- [bpf-next,v5,4/4] bpf, btf: Enforce destructor kfunc type with CFI
https://git.kernel.org/bpf/bpf-next/c/99fde4d06261
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-01-13 3:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-10 8:25 [PATCH bpf-next v5 0/4] Use correct destructor kfunc types Sami Tolvanen
2026-01-10 8:25 ` [PATCH bpf-next v5 1/4] bpf: crypto: Use the correct destructor kfunc type Sami Tolvanen
2026-01-10 18:49 ` kernel test robot
2026-01-10 8:25 ` [PATCH bpf-next v5 2/4] bpf: net_sched: " Sami Tolvanen
2026-01-10 8:25 ` [PATCH bpf-next v5 3/4] selftests/bpf: " Sami Tolvanen
2026-01-10 8:25 ` [PATCH bpf-next v5 4/4] bpf, btf: Enforce destructor kfunc type with CFI Sami Tolvanen
2026-01-12 20:33 ` [PATCH bpf-next v5 0/4] Use correct destructor kfunc types Martin KaFai Lau
2026-01-13 3: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=176827321329.1651449.11456880793258426338.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=samitolvanen@google.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=vadim.fedorenko@linux.dev \
--cc=vmalik@redhat.com \
--cc=xiyou.wangcong@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox