public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
	yonghong.song@linux.dev, kuba@kernel.org
Subject: Re: [PATCH bpf-next v2 0/4] bpf: consolidate pointer offset tracking in var_off
Date: Fri, 13 Feb 2026 23:50:51 +0000	[thread overview]
Message-ID: <177102665132.2575868.15031753627430693514.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260212-ptrs-off-migration-v2-0-00820e4d3438@gmail.com>

Hello:

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

On Thu, 12 Feb 2026 13:34:20 -0800 you wrote:
> Consolidate static and varying pointer offset tracking logic in the
> BPF verifier. All pointer offsets are now represented solely using
> `reg->var_off` and min/max fields, simplifying pointer tracking code
> and making it easier to widen pointer registers for loop convergence
> checks.
> 
> Patch 1 is a preparatory refactoring of check_reg_sane_offset().
> Patch 2 is the main change, moving pointer offsets from `reg->off`
>   to `reg->var_off`.
> Patch 3 removes references to `reg->off` in netronome code.
> Patch 4 renames the now-repurposed `reg->off` field to `reg->delta`,
>   reflecting its remaining role as a constant delta between linked
>   scalar registers.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/4] bpf: split check_reg_sane_offset() in two parts
    https://git.kernel.org/bpf/bpf-next/c/ed20a14309e0
  - [bpf-next,v2,2/4] bpf: use reg->var_off instead of reg->off for pointers
    https://git.kernel.org/bpf/bpf-next/c/022ac0750883
  - [bpf-next,v2,3/4] nfp: bpf: remove references to bpf_reg_state->off for pointers
    https://git.kernel.org/bpf/bpf-next/c/6363fc17c9f5
  - [bpf-next,v2,4/4] bpf: rename bpf_reg_state->off to bpf_reg_state->delta
    https://git.kernel.org/bpf/bpf-next/c/3d91c618aca4

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-02-13 23:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12 21:34 [PATCH bpf-next v2 0/4] bpf: consolidate pointer offset tracking in var_off Eduard Zingerman
2026-02-12 21:34 ` [PATCH bpf-next v2 1/4] bpf: split check_reg_sane_offset() in two parts Eduard Zingerman
2026-02-12 21:34 ` [PATCH bpf-next v2 2/4] bpf: use reg->var_off instead of reg->off for pointers Eduard Zingerman
2026-02-12 21:34 ` [PATCH bpf-next v2 3/4] nfp: bpf: remove references to bpf_reg_state->off " Eduard Zingerman
2026-02-12 21:34 ` [PATCH bpf-next v2 4/4] bpf: rename bpf_reg_state->off to bpf_reg_state->delta Eduard Zingerman
2026-02-13 23:50 ` 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=177102665132.2575868.15031753627430693514.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=kernel-team@fb.com \
    --cc=kuba@kernel.org \
    --cc=martin.lau@linux.dev \
    --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