drm/amdgpu: serialize vblank counter reads against GPU reset

Overview

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: serialize vblank counter reads against GPU reset

The vblank counter callback reads display registers and scanout position without holding reset_domain->sem. During GPU recovery, display commit work can call the callback while reset owns the semaphore for writing. The hardware access then triggers the lockdep_assert_held() in amdgpu_device_skip_hw_access() and sets TAINT_WARN when lockdep is enabled.

Try to acquire the reset semaphore for reading before accessing the hardware, and hold it across the counter and scanout-position reads. If reset is already in progress, return DRM's cached software vblank count instead. This avoids blocking behind reset and avoids accessing display hardware while it is being reset.

The cached count is less accurate than the hardware count, but is used only when reset prevents a safe hardware read. This addresses the reset-time warning from this vblank path; it does not suppress or fix unrelated lockdep warnings.

(cherry picked from commit 51a4359f7431a4be5e42803c8bdaf7e0e5be2934)

Affected

• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 037796d9ca1da97978deaefd88ca5649f6cb69f5
• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 11b6193c8841a052b7907006ffb1e02468b1448e
• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 8d6f773d7479034a574ecc3b585bcd07d46b4824
• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < f4a0a1ce147d1a6e428d7cb5e3b99fd695139fc7
• Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 1a6023edfbb5673f55fab6348f135fb3b1428ea5
• Linux < 6.6.160
• Linux < 6.12.113
• Linux < 6.18.57
• Linux < 7.2.11
• Linux (all versions)

Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.