[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20260128035241.1839686-1-wangqing7171@gmail.com>
Date: Wed, 28 Jan 2026 11:52:41 +0800
From: Qing Wang <wangqing7171@...il.com>
To: syzbot+72a43cdb78469f7fbad1@...kaller.appspotmail.com
Cc: acme@...nel.org,
adrian.hunter@...el.com,
alexander.shishkin@...ux.intel.com,
irogers@...gle.com,
jolsa@...nel.org,
linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org,
mark.rutland@....com,
mingo@...hat.com,
namhyung@...nel.org,
peterz@...radead.org,
syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [perf?] WARNING: suspicious RCU usage in get_callchain_entry
#syz test
diff --git a/kernel/bpf/stackmap.c b/kernel/bpf/stackmap.c
index da3d328f5c15..6e53c2d916cd 100644
--- a/kernel/bpf/stackmap.c
+++ b/kernel/bpf/stackmap.c
@@ -460,8 +460,7 @@ static long __bpf_get_stack(struct pt_regs *regs, struct task_struct *task,
max_depth = stack_map_calculate_max_depth(size, elem_size, flags);
- if (may_fault)
- rcu_read_lock(); /* need RCU for perf's callchain below */
+ rcu_read_lock(); /* need RCU for perf's callchain below */
if (trace_in) {
trace = trace_in;
@@ -474,8 +473,7 @@ static long __bpf_get_stack(struct pt_regs *regs, struct task_struct *task,
}
if (unlikely(!trace) || trace->nr < skip) {
- if (may_fault)
- rcu_read_unlock();
+ rcu_read_unlock();
goto err_fault;
}
Powered by blists - more mailing lists