diff options
| author | Grazvydas Ignotas <[email protected]> | 2016-09-25 23:34:46 +0300 |
|---|---|---|
| committer | Alex Deucher <[email protected]> | 2016-09-27 13:00:51 -0400 |
| commit | 54ddf3a6af537cbfe038f9a2754f26de80c5818b (patch) | |
| tree | 69c4821436f125ff09faff6f71873c913c3d33ba /tools/perf/scripts/python/bin | |
| parent | d8907643cc6b00e96aeb1555f0e0c2930f69c18b (diff) | |
drm/amdgpu: don't leave dangling pointers around
Right now it's possible to trigger fence_drv.fences[] dereference after
the array has been freed. While the real problem is elsewhere, this still
results in confusing errors that depend on how the freed memory was
reused (I've seen "kernel tried to execute NX-protected page"), it's
better to clear them and get NULL dereference so that it's obvious what's
going wrong.
Signed-off-by: Grazvydas Ignotas <[email protected]>
Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions