[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id:
<174965763351.3384611.4699133562202888154.git-patchwork-notify@kernel.org>
Date: Wed, 11 Jun 2025 16:00:33 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Charalampos Mitrodimas <charmitro@...teo.net>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, horms@...nel.org, martin.lau@...ux.dev,
daniel@...earbox.net, john.fastabend@...il.com, ast@...nel.org,
andrii@...nel.org, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, kpsingh@...nel.org, sdf@...ichev.me,
haoluo@...gle.com, jolsa@...nel.org, yangfeng@...inos.cn, tj@...nel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
syzbot+b4169a1cfb945d2ed0ec@...kaller.appspotmail.com
Subject: Re: [PATCH bpf-next v2] net: Fix RCU usage in task_cls_state() for
BPF
programs
Hello:
This patch was applied to bpf/bpf-next.git (net)
by Daniel Borkmann <daniel@...earbox.net>:
On Wed, 11 Jun 2025 09:04:06 +0000 you wrote:
> The commit ee971630f20f ("bpf: Allow some trace helpers for all prog
> types") made bpf_get_cgroup_classid_curr helper available to all BPF
> program types, not just networking programs.
>
> This helper calls __task_get_classid() which internally calls
> task_cls_state() requiring rcu_read_lock_bh_held(). This works in
> networking/tc context where RCU BH is held, but triggers an RCU
> warning when called from other contexts like BPF syscall programs that
> run under rcu_read_lock_trace():
>
> [...]
Here is the summary with links:
- [bpf-next,v2] net: Fix RCU usage in task_cls_state() for BPF programs
https://git.kernel.org/bpf/bpf-next/c/bdcaef7b8815
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists