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
..
drm	drm/amd/display: perform a bounds check before filling dirty rectangles	2023-06-30 13:11:35 -04:00
host1x	drm/tegra: Changes for v6.4-rc1	2023-04-06 15:02:17 +02:00
ipu-v3	ipu-v3: Include <linux/io.h>	2023-05-18 11:06:18 +02:00
trace
vga
Makefile