public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
	eddyz87@gmail.com, memxor@gmail.com, yatsenko@meta.com
Subject: Re: [PATCH bpf-next v2 0/2] bpf: Migrate bpf_task_work and file dynptr to kmalloc_nolock
Date: Thu, 02 Apr 2026 16:40:08 +0000	[thread overview]
Message-ID: <177514800854.525109.2727217490874276359.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260330-kmalloc_special-v2-0-c90403f92ff0@meta.com>

Hello:

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

On Mon, 30 Mar 2026 15:27:55 -0700 you wrote:
> Now that kmalloc can be used from NMI context via kmalloc_nolock(),
> migrate BPF internal allocations away from bpf_mem_alloc to use the
> standard slab allocator.
> 
> Use kfree_rcu() for deferred freeing, which waits for a regular RCU
> grace period before the memory is reclaimed. Sleepable BPF programs
> hold rcu_read_lock_trace but not regular rcu_read_lock, so patch 1
> adds explicit rcu_read_lock/unlock around the pointer-to-refcount
> window to prevent kfree_rcu from freeing memory while a sleepable
> program is still between reading the pointer and acquiring a
> reference.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/2] bpf: Migrate bpf_task_work to kmalloc_nolock
    https://git.kernel.org/bpf/bpf-next/c/90f51ebff242
  - [bpf-next,v2,2/2] bpf: Migrate dynptr file to kmalloc_nolock
    https://git.kernel.org/bpf/bpf-next/c/cc878b414450

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-02 16:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 22:27 [PATCH bpf-next v2 0/2] bpf: Migrate bpf_task_work and file dynptr to kmalloc_nolock Mykyta Yatsenko
2026-03-30 22:27 ` [PATCH bpf-next v2 1/2] bpf: Migrate bpf_task_work " Mykyta Yatsenko
2026-03-31  0:00   ` Andrii Nakryiko
2026-03-31 10:29     ` Mykyta Yatsenko
2026-03-31  0:58   ` Kumar Kartikeya Dwivedi
2026-03-30 22:27 ` [PATCH bpf-next v2 2/2] bpf: Migrate dynptr file " Mykyta Yatsenko
2026-03-31  0:01   ` Andrii Nakryiko
2026-03-31  0:58   ` Kumar Kartikeya Dwivedi
2026-04-02 16: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=177514800854.525109.2727217490874276359.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=kafai@meta.com \
    --cc=kernel-team@meta.com \
    --cc=memxor@gmail.com \
    --cc=mykyta.yatsenko5@gmail.com \
    --cc=yatsenko@meta.com \
    /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