[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220312121913.GA28057@worktop.programming.kicks-ass.net>
Date: Sat, 12 Mar 2022 13:19:13 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Chengming Zhou <zhouchengming@...edance.com>
Cc: tj@...nel.org, lizefan.x@...edance.com, hannes@...xchg.org,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
songmuchun@...edance.com,
Linux Kernel Functional Testing <lkft@...aro.org>,
syzbot+16e3f2c77e7c5a0113f9@...kaller.appspotmail.com,
Zhouyi Zhou <zhouzhouyi@...il.com>
Subject: Re: [PATCH linux-next] cgroup: fix suspicious
rcu_dereference_check() usage warning
On Sat, Mar 05, 2022 at 11:41:03AM +0800, Chengming Zhou wrote:
> task_css_set_check() will use rcu_dereference_check() to check for
> rcu_read_lock_held() on the read-side, which is not true after commit
> dc6e0818bc9a ("sched/cpuacct: Optimize away RCU read lock"). This
> commit drop explicit rcu_read_lock(), change to RCU-sched read-side
> critical section. So fix the RCU warning by adding check for
> rcu_read_lock_sched_held().
>
> Fixes: dc6e0818bc9a ("sched/cpuacct: Optimize away RCU read lock")
> Reported-by: Linux Kernel Functional Testing <lkft@...aro.org>
> Reported-by: syzbot+16e3f2c77e7c5a0113f9@...kaller.appspotmail.com
> Tested-by: Zhouyi Zhou <zhouzhouyi@...il.com>
> Signed-off-by: Chengming Zhou <zhouchengming@...edance.com>
Thanks, I'll go stick this in sched/core so it's in the same branch that
caused the problem.
Powered by blists - more mailing lists