The msm_mapping@shadow test fails on SM8350, which means that the write might get through (hopefully not though). Disable the test completely for now until we can fix the issue.
Link: https://gitlab.freedesktop.org/drm/msm/-/issues/77 Signed-off-by: Dmitry Baryshkov <dmitry.barysh...@oss.qualcomm.com> --- drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt b/drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt index 9450f2a002fd7e68f0f674ac6ac84aeebf28347f..a8b535abc8ef0d996d0c73ece1c7a9622250928e 100644 --- a/drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt +++ b/drivers/gpu/drm/ci/xfails/msm-sm8350-hdk-skips.txt @@ -210,3 +210,8 @@ msm/msm_mapping@ring # [ 229.752499] CPU features: 0x18,00000017,00200928,4200720b # [ 229.758095] Memory Limit: none # [ 229.761291] ---[ end Kernel panic - not syncing: softlockup: hung tasks ]--- + +# Protection doesn't seem to be enforced, don't perform write which might get through +# https://gitlab.freedesktop.org/drm/msm/-/issues/77 +msm/msm_mapping@shadow + --- base-commit: 8f5264d302e803e7ef82a61f9632a0d2ef67413f change-id: 20250513-msm-ci-fixes-3e7ce259d1d9 Best regards, -- Dmitry Baryshkov <dmitry.barysh...@oss.qualcomm.com>
