diff options
author | Ryan Seto <ryanseto@amd.com> | 2024-11-01 17:19:56 +0300 |
---|---|---|
committer | Alex Deucher <alexander.deucher@amd.com> | 2024-11-11 22:05:22 +0300 |
commit | 6825cb07b79ffeb1d90ffaa7a1227462cdca34ae (patch) | |
tree | 3800fb2b14507daac1acfee5edd26273cd1b15b9 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | bd8a9576617439bdc907c9ce0875909aea4221cb (diff) | |
download | linux-6825cb07b79ffeb1d90ffaa7a1227462cdca34ae.tar.xz |
drm/amd/display: Handle dml allocation failure to avoid crash
[Why]
In the case where a dml allocation fails for any reason, the
current state's dml contexts would no longer be valid. Then
subsequent calls dc_state_copy_internal would shallow copy
invalid memory and if the new state was released, a double
free would occur.
[How]
Reset dml pointers in new_state to NULL and avoid invalid
pointer
Reviewed-by: Dillon Varone <dillon.varone@amd.com>
Signed-off-by: Ryan Seto <ryanseto@amd.com>
Signed-off-by: Hamza Mahfooz <hamza.mahfooz@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
(cherry picked from commit bcafdc61529a48f6f06355d78eb41b3aeda5296c)
Cc: stable@vger.kernel.org
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions