public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: bpf@vger.kernel.org, ast@kernel.org, puranjay@kernel.org,
	info@starlabs.sg
Subject: Re: [PATCH bpf-next 1/4] bpf: Fix linked reg delta tracking when src_reg == dst_reg
Date: Wed, 08 Apr 2026 01:20:15 +0000	[thread overview]
Message-ID: <177561121504.25865.1223761626895962170.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260407192421.508817-1-daniel@iogearbox.net>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Tue,  7 Apr 2026 21:24:18 +0200 you wrote:
> Consider the case of rX += rX where src_reg and dst_reg are pointers to
> the same bpf_reg_state in adjust_reg_min_max_vals(). The latter first
> modifies the dst_reg in-place, and later in the delta tracking, the
> subsequent is_reg_const(src_reg)/reg_const_value(src_reg) reads the
> post-{add,sub} value instead of the original source.
> 
> This is problematic since it sets an incorrect delta, which sync_linked_regs()
> then propagates to linked registers, thus creating a verifier-vs-runtime
> mismatch. Fix it by just skipping this corner case.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/4] bpf: Fix linked reg delta tracking when src_reg == dst_reg
    https://git.kernel.org/bpf/bpf-next/c/d7f14173c0d5
  - [bpf-next,2/4] bpf: Clear delta when clearing reg id for non-{add,sub} ops
    https://git.kernel.org/bpf/bpf-next/c/1b327732c846
  - [bpf-next,3/4] selftests/bpf: Add tests for delta tracking when src_reg == dst_reg
    https://git.kernel.org/bpf/bpf-next/c/ed2eecdc0c66
  - [bpf-next,4/4] selftests/bpf: Add tests for stale delta leaking through id reassignment
    https://git.kernel.org/bpf/bpf-next/c/cac16ce1e378

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-04-08  1:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-07 19:24 [PATCH bpf-next 1/4] bpf: Fix linked reg delta tracking when src_reg == dst_reg Daniel Borkmann
2026-04-07 19:24 ` [PATCH bpf-next 2/4] bpf: Clear delta when clearing reg id for non-{add,sub} ops Daniel Borkmann
2026-04-07 19:24 ` [PATCH bpf-next 3/4] selftests/bpf: Add tests for delta tracking when src_reg == dst_reg Daniel Borkmann
2026-04-07 19:24 ` [PATCH bpf-next 4/4] selftests/bpf: Add tests for stale delta leaking through id reassignment Daniel Borkmann
2026-04-08  1: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=177561121504.25865.1223761626895962170.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=info@starlabs.sg \
    --cc=puranjay@kernel.org \
    /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