BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: alexei.starovoitov@gmail.com, bpf@vger.kernel.org, ast@kernel.org
Subject: Re: [PATCH bpf-next] bpf: Free the subprog jump tables once the CFG passes are done
Date: Fri, 16 Oct 2026 17:50:17 +0000	[thread overview]
Message-ID: <179217301777.897417.11449085919420198009.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261016155559.652461-1-daniel@iogearbox.net>

Hello:

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

On Fri, 16 Oct 2026 17:55:59 +0200 you wrote:
> The jump tables which compute_subprog_jts() builds are only read through
> bpf_insn_successors() once CFG discovery is done. Its last caller is
> bpf_compute_scev(), which runs after bpf_compute_live_registers(), so
> free the tables right after it instead of keeping them until the verifier
> environment is torn down. With large insn_array maps, this also drops them
> before do_check() starts to allocate states.
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: Free the subprog jump tables once the CFG passes are done
    https://git.kernel.org/bpf/bpf-next/c/d2141481a764

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2026-10-16 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 15:55 [PATCH bpf-next] bpf: Free the subprog jump tables once the CFG passes are done Daniel Borkmann
2026-10-16 17: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=179217301777.897417.11449085919420198009.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    /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