Hamza Mahfooz af22d6a869 drm/amd/display: perform a bounds check before filling dirty rectangles ... Currently, it is possible for us to access memory that we shouldn't. Since, we acquire (possibly dangling) pointers to dirty rectangles before doing a bounds check to make sure we can actually accommodate the number of dirty rectangles userspace has requested to fill. This issue is especially evident if a compositor requests both MPO and damage clips at the same time, in which case I have observed a soft-hang. So, to avoid this issue, perform the bounds check before filling a single dirty rectangle and WARN() about it, if it is ever attempted in fill_dc_dirty_rect(). Cc: stable@vger.kernel.org # 6.1+ Fixes: 30ebe41582 ("drm/amd/display: add FB_DAMAGE_CLIPS support") Reviewed-by: Leo Li <sunpeng.li@amd.com> Signed-off-by: Hamza Mahfooz <hamza.mahfooz@amd.com> Signed-off-by: Alex Deucher <alexander.deucher@amd.com>		2023-06-30 13:11:35 -04:00
..
amdgpu_dm	drm/amd/display: perform a bounds check before filling dirty rectangles	2023-06-30 13:11:35 -04:00
dc	drm/amd/display: 3.2.240	2023-06-23 15:46:12 -04:00
dmub	Revert "drm/amd/display: cache trace buffer size"	2023-06-09 12:50:08 -04:00
include	drm/amd/display: fix compilation error due to shifting negative value	2023-06-09 12:38:19 -04:00
modules	drm/amd: Disable PSR-SU on Parade 0803 TCON	2023-06-30 13:11:30 -04:00
Kconfig	Merge tag 'amd-drm-next-6.5-2023-06-09' of https://gitlab.freedesktop.org/agd5f/linux into drm-next	2023-06-15 14:11:22 +10:00
Makefile	drm/amd/display: Drop CONFIG_DRM_AMD_DC_HDCP	2023-03-07 14:22:39 -05:00
TODO