BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Anton Protopopov <a.s.protopopov@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org
Subject: Re: [PATCH bpf-next] bpf: cleanup aux->used_maps after jit
Date: Mon, 24 Nov 2025 17:50:06 +0000	[thread overview]
Message-ID: <176400660652.23470.12746953403702208767.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251124151515.2543403-1-a.s.protopopov@gmail.com>

Hello:

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

On Mon, 24 Nov 2025 15:15:15 +0000 you wrote:
> In commit b4ce5923e780 ("bpf, x86: add new map type: instructions array")
> env->used_map was copied to func[i]->aux->used_maps before jitting.
> Clear these fields out after jitting such that pointer to freed memory
> (env->used_maps is freed later) are not kept in a live data structure.
> 
> The reason why the copies were initially added is explained in
> https://lore.kernel.org/bpf/20251105090410.1250500-1-a.s.protopopov@gmail.com
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: cleanup aux->used_maps after jit
    https://git.kernel.org/bpf/bpf-next/c/fad804002ef3

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



      parent reply	other threads:[~2025-11-24 17:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 15:15 [PATCH bpf-next] bpf: cleanup aux->used_maps after jit Anton Protopopov
2025-11-24 15:30 ` bot+bpf-ci
2025-11-24 15:56   ` Chris Mason
2025-11-24 16:55     ` Alexei Starovoitov
2025-11-24 17:40       ` Chris Mason
2025-11-24 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=176400660652.23470.12746953403702208767.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=a.s.protopopov@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.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