From: "Emil Tsalapatis" <emil@etsalapatis.com>
To: "Emil Tsalapatis" <emil@etsalapatis.com>, <bpf@vger.kernel.org>
Cc: <ast@kernel.org>, <andrii@kernel.org>, <eddyz87@gmail.com>,
<memxor@gmail.com>, <daniel@iogearbox.net>,
"Puranjay Mohan" <puranjay@kernel.org>
Subject: Re: [PATCH bpf-next v4 0/8] bpf: Fix arena memory incoherence
Date: Fri, 16 Oct 2026 00:04:55 +0000 [thread overview]
Message-ID: <DM5TNKREPDWB.2OEYD0RXX572F@etsalapatis.com> (raw)
In-Reply-To: <DM5TMNILXYE6.3EKVZL31MY64O@etsalapatis.com>
On Fri Oct 16, 2026 at 12:03 AM UTC, Emil Tsalapatis wrote:
> On Wed Oct 14, 2026 at 11:34 PM UTC, Emil Tsalapatis wrote:
>> Setting up arena memory for a task currently requires two operations:
>> Adjusting its range tree, used for tracking which memory is allocated;
>> and adjusting its page tables/flushing its TLB state. These operations
>> cannot happen atomically because their critical sections do not nest.
>> This lack of atomicity is the source of two bugs that can lead to
>> incoherence between different users of the same arena, wherein they
>> observe different pages for the same address.
>>
>> Address the problem by more finely tracking the state of each address.
>> Expand the range tree used for address state tracking with a third
>> state, used to denote whether an address range is unavailable, either
>> because it is being freed or because it is being populated by a VM
>> fault. Use this extra state in the arena page freeing/fault logic
>> to ensure that operations on a single address properly serialize.
>>
>> Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
>> Cc: Puranjay Mohan <puranjay@kernel.org>
>
> I also have an alternative fix that is way simpler at the cost of holding
> the arena lock for longer during frees. I think it's a perfectly acceptable
> tradeoff since applications are expected to leave off actual page allocation/
> freeing to the allocator, and the allocator shouldn't be constantly churning
> the mapping with kfunc calls.
Sorry for the double email, forgot to actually add the link to the patchset
(just posting the link for now to avoid having two parallel extant versions here):
https://github.com/etsal/linux/tree/arena_race
>
>>
>> v3 -> v4 (https://lore.kernel.org/bpf/20260923191125.5311-1-emil@etsalapatis.com/)
>>
>> - Add per-arena anonymous mappings and associate pages with them
>> - Return VM_FAULT_LOCKED and let generic MM install user PTEs; wait
>> for locked fault pages before TLB flushing and zapping (Alexei).
>> - Add mutual exclusion between arena free and fault operations to
>> prevent incoherency.
>> - Return VM_FAULT_NOPAGE for non-retryable GUP faults when progress is
>> impossible.
>> - Stop and drain self-requeueing deferred frees before map teardown.
>> - Track ownership of unavailable ranges independently of free progress
>> and retry worker reservations on -ENOMEM without starting teardown.
>> - Make arena free span state machine explicit.
>>
>> v2 -> v3 (https://lore.kernel.org/bpf/20260923061425.7045-1-emil@etsalapatis.com/)
>>
>> - Rebase on bpf-next and resolve conflicts
>> - Fold in the atomic mark_available range tree operation into initial
>> fix patches
>>
>> v1 -> v2 (https://lore.kernel.org/bpf/20260902070239.16968-1-emil@etsalapatis.com/)
>>
>> - Use __range_iter_next() in is_range_tree_set() (bot-ci)
>> - Move -EAGAIN handling to the patch where the errno is introduced (bot-ci)
>> - Add refactoring patch for (Puranjay)
>> - Avoid leaking unavailable range tree nodes with atomic mark_available
>> operation()
>> - Avoid retries on res spinlock locking for -EDEADLK (Puranjay)
>>
>>
>> Emil Tsalapatis (8):
>> bpf: Use mapping tree to zap arena VMAs
>> bpf: Associate arena pages with their mapping
>> bpf: arena: Stop deferred frees before map teardown
>> bpf: Update is_range_tree_set to work for consecutive ranges
>> bpf: Track availability information for ranges in range tree
>> bpf: Fix arena race between page free and alloc leading to incoherency
>> bpf: Synchronize arena page faults with page freeing
>> selftests/bpf: Add arena allocation race tests
>>
>> include/linux/bpf.h | 1 +
>> kernel/bpf/arena.c | 452 ++++++++++++++----
>> kernel/bpf/range_tree.c | 240 ++++++++--
>> kernel/bpf/range_tree.h | 7 +-
>> kernel/bpf/syscall.c | 2 +
>> .../selftests/bpf/prog_tests/arena_race.c | 285 +++++++++++
>> .../testing/selftests/bpf/progs/arena_race.c | 159 ++++++
>> 7 files changed, 1013 insertions(+), 133 deletions(-)
>> create mode 100644 tools/testing/selftests/bpf/prog_tests/arena_race.c
>> create mode 100644 tools/testing/selftests/bpf/progs/arena_race.c
next prev parent reply other threads:[~2026-10-16 0:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 23:34 [PATCH bpf-next v4 0/8] bpf: Fix arena memory incoherence Emil Tsalapatis
2026-10-14 23:34 ` [PATCH bpf-next v4 1/8] bpf: Use mapping tree to zap arena VMAs Emil Tsalapatis
2026-10-15 0:33 ` bot+bpf-ci
2026-10-15 15:02 ` Emil Tsalapatis
2026-10-16 2:02 ` Alexei Starovoitov
2026-10-14 23:34 ` [PATCH bpf-next v4 2/8] bpf: Associate arena pages with their mapping Emil Tsalapatis
2026-10-15 0:01 ` sashiko-bot
2026-10-15 15:15 ` Emil Tsalapatis
2026-10-16 2:02 ` Alexei Starovoitov
2026-10-14 23:34 ` [PATCH bpf-next v4 3/8] bpf: arena: Stop deferred frees before map teardown Emil Tsalapatis
2026-10-14 23:34 ` [PATCH bpf-next v4 4/8] bpf: Update is_range_tree_set to work for consecutive ranges Emil Tsalapatis
2026-10-14 23:34 ` [PATCH bpf-next v4 5/8] bpf: Track availability information for ranges in range tree Emil Tsalapatis
2026-10-14 23:34 ` [PATCH bpf-next v4 6/8] bpf: Fix arena race between page free and alloc leading to incoherency Emil Tsalapatis
2026-10-16 2:02 ` Alexei Starovoitov
2026-10-14 23:34 ` [PATCH bpf-next v4 7/8] bpf: Synchronize arena page faults with page freeing Emil Tsalapatis
2026-10-15 0:33 ` bot+bpf-ci
2026-10-15 15:18 ` Emil Tsalapatis
2026-10-16 2:02 ` Alexei Starovoitov
2026-10-14 23:34 ` [PATCH bpf-next v4 8/8] selftests/bpf: Add arena allocation race tests Emil Tsalapatis
2026-10-14 23:52 ` sashiko-bot
2026-10-16 0:03 ` [PATCH bpf-next v4 0/8] bpf: Fix arena memory incoherence Emil Tsalapatis
2026-10-16 0:04 ` Emil Tsalapatis [this message]
2026-10-16 2:03 ` Alexei Starovoitov
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=DM5TNKREPDWB.2OEYD0RXX572F@etsalapatis.com \
--to=emil@etsalapatis.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.