From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: 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,
emil@etsalapatis.com, ihor.solodrai@linux.dev,
kernel-team@meta.com, hca@linux.ibm.com, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org, yatsenko@meta.com
Subject: Re: [PATCH bpf-next] bpf: Fix CFI mismatch in task work callback
Date: Fri, 24 Jul 2026 20:40:12 +0000 [thread overview]
Message-ID: <178492561215.3300548.13290729767393088788.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260724-task_work_cfi-v1-1-2616691781ed@meta.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:
On Fri, 24 Jul 2026 08:52:06 -0700 you wrote:
> From: Mykyta Yatsenko <yatsenko@meta.com>
>
> BPF subprograms use the bpf_callback_t ABI, but task work invokes the
> callback through a three-argument function pointer. This trips kCFI.
>
> Store and invoke the callback as bpf_callback_t.
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Fix CFI mismatch in task work callback
https://git.kernel.org/bpf/bpf-next/c/2805abd08957
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-24 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 15:52 [PATCH bpf-next] bpf: Fix CFI mismatch in task work callback Mykyta Yatsenko
2026-07-24 20: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=178492561215.3300548.13290729767393088788.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=emil@etsalapatis.com \
--cc=hca@linux.ibm.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=song@kernel.org \
--cc=yatsenko@meta.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