From: Yonghong Song <yonghong.song@linux.dev>
To: KaFai Wan <kafai.wan@linux.dev>,
ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, shuah@kernel.org,
toke@redhat.com, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: Le Chen <tom2cat@sjtu.edu.cn>
Subject: Re: [PATCH bpf v2 1/2] bpf: Avoid RCU context warning when unpinning htab with internal structs
Date: Mon, 6 Oct 2025 21:05:23 -0700 [thread overview]
Message-ID: <2e24a7e9-fe8c-4af8-b775-ccc75e6af091@linux.dev> (raw)
In-Reply-To: <20251007012235.755853-2-kafai.wan@linux.dev>
On 10/6/25 6:22 PM, KaFai Wan wrote:
> When unpinning a BPF hash table (htab or htab_lru) that contains internal
> structures (timer, workqueue, or task_work) in its values, a BUG warning
> is triggered:
> BUG: sleeping function called from invalid context at kernel/bpf/hashtab.c:244
> in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 14, name: ksoftirqd/0
> ...
>
> The issue arises from the interaction between BPF object unpinning and
> RCU callback mechanisms:
> 1. BPF object unpinning uses ->free_inode() which schedules cleanup via
> call_rcu(), deferring the actual freeing to an RCU callback that
> executes within the RCU_SOFTIRQ context.
> 2. During cleanup of hash tables containing internal structures,
> htab_map_free_internal_structs() is invoked, which includes
> cond_resched() or cond_resched_rcu() calls to yield the CPU during
> potentially long operations.
>
> However, cond_resched() or cond_resched_rcu() cannot be safely called from
> atomic RCU softirq context, leading to the BUG warning when attempting
> to reschedule.
>
> Fix this by changing from ->free_inode() to ->destroy_inode() and rename
> bpf_free_inode() to bpf_destroy_inode() for BPF objects (prog, map, link).
> This allows direct inode freeing without RCU callback scheduling,
> avoiding the invalid context warning.
>
> Reported-by: Le Chen <tom2cat@sjtu.edu.cn>
> Closes: https://lore.kernel.org/all/1444123482.1827743.1750996347470.JavaMail.zimbra@sjtu.edu.cn/
> Fixes: 68134668c17f ("bpf: Add map side support for bpf timers.")
> Suggested-by: Alexei Starovoitov <ast@kernel.org>
> Signed-off-by: KaFai Wan <kafai.wan@linux.dev>
Acked-by: Yonghong Song <yonghong.song@linux.dev>
next prev parent reply other threads:[~2025-10-07 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-07 1:22 [PATCH bpf v2 0/2] bpf: Avoid RCU context warning when unpinning htab with internal structs KaFai Wan
2025-10-07 1:22 ` [PATCH bpf v2 1/2] " KaFai Wan
2025-10-07 4:05 ` Yonghong Song [this message]
2025-10-07 1:22 ` [PATCH bpf v2 2/2] selftests/bpf: Add test for unpinning htab with internal timer struct KaFai Wan
2025-10-07 4:04 ` Yonghong Song
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=2e24a7e9-fe8c-4af8-b775-ccc75e6af091@linux.dev \
--to=yonghong.song@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai.wan@linux.dev \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.org \
--cc=song@kernel.org \
--cc=toke@redhat.com \
--cc=tom2cat@sjtu.edu.cn \
/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