From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, puranjay12@gmail.com, ast@kernel.org,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
eddyz87@gmail.com, memxor@gmail.com, mykyta.yatsenko5@gmail.com,
kernel-team@meta.com
Subject: Re: [PATCH bpf v6 0/3] bpf: fix and improve open-coded task_vma iterator
Date: Fri, 10 Apr 2026 19:10:10 +0000 [thread overview]
Message-ID: <177584821030.2607283.14843018768644433891.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260408154539.3832150-1-puranjay@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 8 Apr 2026 08:45:34 -0700 you wrote:
> Changelog:
> v5: https://lore.kernel.org/all/20260326151111.4002475-1-puranjay@kernel.org/
> Changes in v6:
> - Replace local_irq_disable() + get_task_mm() with spin_trylock() on
> alloc_lock to avoid a softirq deadlock: if the target task holds its
> alloc_lock and gets interrupted, a softirq BPF program iterating
> that task would deadlock on task_lock() (Gemini)
> - Gate on CONFIG_MMU in patch 1 so that the mmput() fallback in
> bpf_iter_mmput_async() cannot sleep in non-sleepable BPF context
> on NOMMU; patch 2 tightens this to CONFIG_PER_VMA_LOCK (Gemini)
> - Merge the split if (irq_work_busy) / if (!mmap_read_trylock())
> back into a single if statement in patch 1 (Andrii)
> - Flip comparison direction in bpf_iter_task_vma_find_next() so both
> the locked and unlocked VMA failure cases read consistently:
> end <= next_addr → PAGE_SIZE, else - use end (Andrii)
> - Add Acked-by from Andrii on patch 3
>
> [...]
Here is the summary with links:
- [bpf,v6,1/3] bpf: fix mm lifecycle in open-coded task_vma iterator
https://git.kernel.org/bpf/bpf-next/c/d8e27d2d22b6
- [bpf,v6,2/3] bpf: switch task_vma iterator from mmap_lock to per-VMA locks
https://git.kernel.org/bpf/bpf-next/c/bee9ef4a40a2
- [bpf,v6,3/3] bpf: return VMA snapshot from task_vma iterator
https://git.kernel.org/bpf/bpf-next/c/4cbee026db54
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-04-10 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 15:45 [PATCH bpf v6 0/3] bpf: fix and improve open-coded task_vma iterator Puranjay Mohan
2026-04-08 15:45 ` [PATCH bpf v6 1/3] bpf: fix mm lifecycle in " Puranjay Mohan
2026-04-08 15:45 ` [PATCH bpf v6 2/3] bpf: switch task_vma iterator from mmap_lock to per-VMA locks Puranjay Mohan
2026-04-08 15:45 ` [PATCH bpf v6 3/3] bpf: return VMA snapshot from task_vma iterator Puranjay Mohan
2026-04-09 13:15 ` Mykyta Yatsenko
2026-04-10 19:10 ` 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=177584821030.2607283.14843018768644433891.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@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=puranjay12@gmail.com \
--cc=puranjay@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