mirror of
git://nv-tegra.nvidia.com/linux-nvgpu.git
synced 2025-12-22 09:12:24 +03:00
2eabcdb8a4
Both profiler and debugger device nodes access and update the list, g->profiler_objects. List operations were currently not guarded by lock thus leading to synchronisation issues. Stress-ng test attempts to trigger repeated random open close sessions on all the device nodes exposed by gpu. This results in kernel panic at random stages of test. Failure signature - Profiler node receives a release call and as part of it, nvgpu_profiler_free attempts to delete the prof_obj_entry and free the prof memory. Simulataneously debugger node also receives a release call and as part of gk20a_dbg_gpu_dev_release, nvgpu attempts to access g->profiler_objects to check for any profiling sessions associated with debugger node. There is a race to access the list which results in kernel panic for address 0x8 because nvgpu tries to access prof_obj->session_id which is at offset 0x8. As part of this change, g->profiler_objects list access/update is guarded with a mutex lock. Bug 4858627 Change-Id: I1e2cf8d27d195bbc9c012cf511029de9eaadb038 Signed-off-by: Kishan Palankar <kpalankar@nvidia.com> Reviewed-on: https://git-master.nvidia.com/r/c/linux-nvgpu/+/3239897 GVS: buildbot_gerritrpt <buildbot_gerritrpt@nvidia.com> Reviewed-by: Sagar Kamble <skamble@nvidia.com> Reviewed-by: Ankur Kishore <ankkishore@nvidia.com>