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
Subject: Re: [PATCH bpf-next v4 00/14] bpf: static stack liveness data flow analysis
Date: Fri, 10 Apr 2026 22:40:29 +0000	[thread overview]
Message-ID: <177586082939.2670415.9674652667360393346.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260410-patch-set-v4-0-5d4eecb343db@gmail.com>

Hello:

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

On Fri, 10 Apr 2026 13:55:51 -0700 you wrote:
> This patch set converts current dynamic stack slot liveness tracking
> mechanism to a static data flow analysis. The result is used during
> state pruning (clean_verifier_state): to zero out dead stack slots,
> enabling more aggressive state equivalence and pruning. To improve
> analysis precision live stack slot tracking is converted to 4-byte
> granularity.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,01/14] bpf: share several utility functions as internal API
    https://git.kernel.org/bpf/bpf-next/c/33dfc521c20d
  - [bpf-next,v4,02/14] bpf: save subprogram name in bpf_subprog_info
    https://git.kernel.org/bpf/bpf-next/c/cf3ee1ecf346
  - [bpf-next,v4,03/14] bpf: Add spis_*() helpers for 4-byte stack slot bitmasks
    https://git.kernel.org/bpf/bpf-next/c/2ad45b414b87
  - [bpf-next,v4,04/14] bpf: make liveness.c track stack with 4-byte granularity
    https://git.kernel.org/bpf/bpf-next/c/7ca5f68cda07
  - [bpf-next,v4,05/14] bpf: 4-byte precise clean_verifier_state
    https://git.kernel.org/bpf/bpf-next/c/be23266b4a08
  - [bpf-next,v4,06/14] bpf: prepare liveness internal API for static analysis pass
    https://git.kernel.org/bpf/bpf-next/c/8d3219f64d98
  - [bpf-next,v4,07/14] bpf: introduce forward arg-tracking dataflow analysis
    https://git.kernel.org/bpf/bpf-next/c/bf0c571f7feb
  - [bpf-next,v4,08/14] bpf: record arg tracking results in bpf_liveness masks
    https://git.kernel.org/bpf/bpf-next/c/fed53dbcdb61
  - [bpf-next,v4,09/14] bpf: simplify liveness to use (callsite, depth) keyed func_instances
    (no matching commit)
  - [bpf-next,v4,10/14] bpf: change logging scheme for live stack analysis
    https://git.kernel.org/bpf/bpf-next/c/2c167d91775b
  - [bpf-next,v4,11/14] selftests/bpf: update existing tests due to liveness changes
    https://git.kernel.org/bpf/bpf-next/c/b42eb55f6ca2
  - [bpf-next,v4,12/14] selftests/bpf: adjust verifier_log buffers
    https://git.kernel.org/bpf/bpf-next/c/957c30c06748
  - [bpf-next,v4,13/14] selftests/bpf: add new tests for static stack liveness analysis
    https://git.kernel.org/bpf/bpf-next/c/27417e5eb9cd
  - [bpf-next,v4,14/14] bpf: poison dead stack slots
    https://git.kernel.org/bpf/bpf-next/c/2cb27158adb3

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-10 22:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10 20:55 [PATCH bpf-next v4 00/14] bpf: static stack liveness data flow analysis Eduard Zingerman
2026-04-10 20:55 ` [PATCH bpf-next v4 01/14] bpf: share several utility functions as internal API Eduard Zingerman
2026-04-10 20:55 ` [PATCH bpf-next v4 02/14] bpf: save subprogram name in bpf_subprog_info Eduard Zingerman
2026-04-10 20:55 ` [PATCH bpf-next v4 03/14] bpf: Add spis_*() helpers for 4-byte stack slot bitmasks Eduard Zingerman
2026-04-10 20:55 ` [PATCH bpf-next v4 04/14] bpf: make liveness.c track stack with 4-byte granularity Eduard Zingerman
2026-04-10 20:55 ` [PATCH bpf-next v4 05/14] bpf: 4-byte precise clean_verifier_state Eduard Zingerman
2026-04-10 20:55 ` [PATCH bpf-next v4 06/14] bpf: prepare liveness internal API for static analysis pass Eduard Zingerman
2026-04-10 20:55 ` [PATCH bpf-next v4 07/14] bpf: introduce forward arg-tracking dataflow analysis Eduard Zingerman
2026-04-10 21:44   ` bot+bpf-ci
2026-04-10 21:46     ` Eduard Zingerman
2026-04-10 22:17       ` Alexei Starovoitov
2026-04-10 20:55 ` [PATCH bpf-next v4 08/14] bpf: record arg tracking results in bpf_liveness masks Eduard Zingerman
2026-04-10 20:56 ` [PATCH bpf-next v4 09/14] bpf: simplify liveness to use (callsite, depth) keyed func_instances Eduard Zingerman
2026-04-10 21:39   ` Paul Chaignon
2026-04-10 21:42     ` Eduard Zingerman
2026-04-10 21:44   ` bot+bpf-ci
2026-04-10 22:33     ` Alexei Starovoitov
2026-04-10 20:56 ` [PATCH bpf-next v4 10/14] bpf: change logging scheme for live stack analysis Eduard Zingerman
2026-04-10 20:56 ` [PATCH bpf-next v4 11/14] selftests/bpf: update existing tests due to liveness changes Eduard Zingerman
2026-04-10 20:56 ` [PATCH bpf-next v4 12/14] selftests/bpf: adjust verifier_log buffers Eduard Zingerman
2026-04-10 20:56 ` [PATCH bpf-next v4 13/14] selftests/bpf: add new tests for static stack liveness analysis Eduard Zingerman
2026-04-10 20:56 ` [PATCH bpf-next v4 14/14] bpf: poison dead stack slots Eduard Zingerman
2026-04-10 22: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=177586082939.2670415.9674652667360393346.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=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