From: patchwork-bot+netdevbpf@kernel.org
To: MingTao Huang <1037827920@qq.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
bpf@vger.kernel.org, john.fastabend@gmail.com,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org,
linux-kernel@vger.kernel.org, mintaohuang@tencent.com
Subject: Re: [PATCH bpf] bpf: Fix stale offload->prog pointer after constant blinding
Date: Mon, 06 Apr 2026 02:00:05 +0000 [thread overview]
Message-ID: <177544080529.2523223.7238691313202506498.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_BCF692F45859CCE6C22B7B0B64827947D406@qq.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 2 Apr 2026 20:18:50 +0800 you wrote:
> From: MingTao Huang <mintaohuang@tencent.com>
>
> When a dev-bound-only BPF program (BPF_F_XDP_DEV_BOUND_ONLY) undergoes
> JIT compilation with constant blinding enabled (bpf_jit_harden >= 2),
> bpf_jit_blind_constants() clones the program. The original prog is then
> freed in bpf_jit_prog_release_other(), which updates aux->prog to point
> to the surviving clone, but fails to update offload->prog.
>
> [...]
Here is the summary with links:
- [bpf] bpf: Fix stale offload->prog pointer after constant blinding
https://git.kernel.org/bpf/bpf-next/c/a1aa9ef47c29
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-04-06 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 12:18 [PATCH bpf] bpf: Fix stale offload->prog pointer after constant blinding MingTao Huang
2026-04-06 2: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=177544080529.2523223.7238691313202506498.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=1037827920@qq.com \
--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=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mintaohuang@tencent.com \
--cc=sdf@fomichev.me \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox