diff options
| author | Zqiang <qiang1.zhang@intel.com> | 2022-07-31 18:53:56 +0800 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@kernel.org> | 2022-09-01 10:50:04 -0700 |
| commit | 48297a22a39adcde7a3ba52b913c5aaa9a990364 (patch) | |
| tree | 1d6348252608aa279adc88789808dd0268e2ad1f /drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | |
| parent | 7634b1eaa0cd135d5eedadb04ad3c91b1ecf28a9 (diff) | |
rcutorture: Use the barrier operation specified by cur_ops
The rcutorture_oom_notify() function unconditionally invokes
rcu_barrier(), which is OK when the rcutorture.torture_type value is
"rcu", but unhelpful otherwise. The purpose of these barrier calls is to
wait for all outstanding callback-flooding callbacks to be invoked before
cleaning up their data. Using the wrong barrier function therefore
risks arbitrary memory corruption. Thus, this commit changes these
rcu_barrier() calls into cur_ops->cb_barrier() to make things work when
torturing non-vanilla flavors of RCU.
Signed-off-by: Zqiang <qiang1.zhang@intel.com>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_object.c')
0 files changed, 0 insertions, 0 deletions