diff options
author | Tejun Heo <tj@kernel.org> | 2013-12-06 15:11:55 -0500 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2013-12-06 15:11:55 -0500 |
commit | 87fb54f1b5a447662854f176eeb1ba92d5ffc1d5 (patch) | |
tree | 1f71a8a0173d19d94db417f4773056669394cd78 /tools/perf/scripts/python/event_analyzing_sample.py | |
parent | e58e1ca438a51e7e5a28f8c9fb342d6f908d92c6 (diff) |
cgroup: css iterations and css_from_dir() are safe under cgroup_mutex
Currently, all css iterations and css_from_dir() require RCU read lock
whether the caller is holding cgroup_mutex or not, which is
unnecessarily restrictive. They are all safe to use under
cgroup_mutex without holding RCU read lock.
Factor out cgroup_assert_mutex_or_rcu_locked() from css_from_id() and
apply it to all css iteration functions and css_from_dir().
v2: cgroup_assert_mutex_or_rcu_locked() definition doesn't need to be
inside CONFIG_PROVE_RCU ifdef as rcu_lockdep_assert() is always
defined and conditionalized. Move it outside of the ifdef block.
Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: Li Zefan <lizefan@huawei.com>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions