diff options
| author | Waiman Long <longman@redhat.com> | 2022-02-02 22:31:03 -0500 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2022-02-08 18:30:41 +0100 |
| commit | 557727313534d9f92e782179372833fd3499f231 (patch) | |
| tree | e62bbce9ad265db6d52b18db11d235e96238b517 /net/sched/act_meta_skbtcindex.c | |
| parent | f1f7d1a22fd73034af73d51086b2fe2981d02028 (diff) | |
| download | linux-stable-557727313534d9f92e782179372833fd3499f231.tar.gz linux-stable-557727313534d9f92e782179372833fd3499f231.tar.bz2 linux-stable-557727313534d9f92e782179372833fd3499f231.zip | |
cgroup/cpuset: Fix "suspicious RCU usage" lockdep warning
commit 2bdfd2825c9662463371e6691b1a794e97fa36b4 upstream.
It was found that a "suspicious RCU usage" lockdep warning was issued
with the rcu_read_lock() call in update_sibling_cpumasks(). It is
because the update_cpumasks_hier() function may sleep. So we have
to release the RCU lock, call update_cpumasks_hier() and reacquire
it afterward.
Also add a percpu_rwsem_assert_held() in update_sibling_cpumasks()
instead of stating that in the comment.
Fixes: 4716909cc5c5 ("cpuset: Track cpusets that use parent's effective_cpus")
Signed-off-by: Waiman Long <longman@redhat.com>
Tested-by: Phil Auld <pauld@redhat.com>
Reviewed-by: Phil Auld <pauld@redhat.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/sched/act_meta_skbtcindex.c')
0 files changed, 0 insertions, 0 deletions