From: bot+bpf-ci@kernel.org
To: leitao@debian.org,ast@kernel.org,daniel@iogearbox.net,andrii@kernel.org,eddyz87@gmail.com,memxor@gmail.com,martin.lau@linux.dev,song@kernel.org,yonghong.song@linux.dev,jolsa@kernel.org,emil@etsalapatis.com,ihor.solodrai@linux.dev,brho@google.com
Cc: bpf@vger.kernel.org,linux-kernel@vger.kernel.org,kernel-team@meta.com,leitao@debian.org,ast@kernel.org,andrii@kernel.org,daniel@iogearbox.net,martin.lau@kernel.org,eddyz87@gmail.com,yonghong.song@linux.dev,clm@meta.com,ihor.solodrai@linux.dev
Subject: Re: [PATCH] bpf: arena: reschedule while freeing the arena pages
Date: Mon, 24 Aug 2026 17:48:01 +0000 (UTC) [thread overview]
Message-ID: <812c7dce29c7faba7596961a4db56703bbb8ecf1ca5b05b30bfeda0f3ca15de0@mail.kernel.org> (raw)
In-Reply-To: <20260824-b4-bpf-arena-free-resched-v1-1-5c447477a64b@debian.org>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
> bpf: arena: reschedule while freeing the arena pages
>
> On non-preemptible kernels that is long enough to trip both the RCU
> stall detector and the softlockup watchdog. Observed on production arm64
> hosts at Meta:
>
> rcu: INFO: rcu_sched self-detected stall on CPU
> rcu: 37-....: (20999 ticks this GP) idle=3834/1/0x4000000000000000
> Workqueue: events_unbound bpf_map_free_deferred
> Call trace:
> __apply_to_page_range+0x404/0x518
> apply_to_existing_page_range+0x18/0x28
> arena_map_free+0x54/0x98
> bpf_map_free_deferred+0x70/0xf8
> process_scheduled_works+0x17c/0x400
> worker_thread+0x198/0x498
> [...]
> watchdog: BUG: soft lockup - CPU#37 stuck for 44s! [kworker/u288:15]
> Kernel panic - not syncing: softlockup: hung tasks
>
> arena_map_free() sweeps the whole 4GiB arena address range in a single
> apply_to_existing_page_range() call and drops every populated page from
> the walk callback.
>
> Give up the CPU after releasing each page, using cond_resched().
This isn't a bug, but the opening sentence "On non-preemptible kernels
that is long enough ..." uses "that" without an antecedent. The phrase
that explains what takes long enough (the 4GiB arena sweep) appears two
paragraphs later, after the stall trace.
Would moving the arena_map_free() description ahead of the stall trace
make the flow clearer?
---
AI reviewed your patch. Please fix the bug or email reply why it's not a bug.
See: https://github.com/kernel-patches/vmtest/blob/master/ci/claude/README.md
CI run summary: https://github.com/kernel-patches/bpf/actions/runs/32755827346
prev parent reply other threads:[~2026-08-24 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 16:54 Breno Leitao
2026-08-24 17:48 ` bot+bpf-ci [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=812c7dce29c7faba7596961a4db56703bbb8ecf1ca5b05b30bfeda0f3ca15de0@mail.kernel.org \
--to=bot+bpf-ci@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brho@google.com \
--cc=clm@meta.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=ihor.solodrai@linux.dev \
--cc=jolsa@kernel.org \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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
all inboxes | Powered by JetHome®