diff options
author | 2013-06-21 15:52:33 -0700 | |
---|---|---|
committer | 2013-06-26 10:48:48 -0700 | |
commit | a4ea1cc90604df08d471ae84eb9627319d10c844 (patch) | |
tree | 73e12ef6845c5cf5bac0b8a2e4e6c4dd03af0a1b /tools/perf/scripts/python/export-to-postgresql.py | |
parent | cgroup: fix RCU accesses around task->cgroups (diff) | |
download | linux-dev-a4ea1cc90604df08d471ae84eb9627319d10c844.tar.xz linux-dev-a4ea1cc90604df08d471ae84eb9627319d10c844.zip |
cgroup: always use RCU accessors for protected accesses
kernel/cgroup.c still has places where a RCU pointer is set and
accessed directly without going through RCU_INIT_POINTER() or
rcu_dereference_protected(). They're all properly protected accesses
so nothing is broken but it leads to spurious sparse RCU address space
warnings.
Substitute direct accesses with RCU_INIT_POINTER() and
rcu_dereference_protected(). Note that %true is specified as the
extra condition for all derference updates. This isn't ideal as all
it does is suppressing warning without actually policing
synchronization rules; however, most are scheduled to be removed
pretty soon along with css_id itself, so no reason to be more
elaborate.
Combined with the previous changes, this removes all RCU related
sparse warnings from cgroup.
Signed-off-by: Tejun Heo <tj@kernel.org>
Reported-by: Fengguang Wu <fengguang.wu@intel.com>
Acked-by; Li Zefan <lizefan@huawei.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions