You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GPU and driver version: Intel(R) Graphics (ADL GT2) (Mesa 24.0.4)
SDK or header version if building from repo: v1.3.275
Options enabled (synchronization, best practices, etc.): N/A
Describe the Issue
The new validation introduced in #7199 regressed the UB fix made in ce2c6ef and reintroduced the crashes in reported in #5649 and #5687 (though now it's now crashing during vkBindImageMemory() rather than vkCreateImage() ). AFAICT, this regression was first released in v1.3.275 and persists today in v1.3.280.
Thanks for digging up all this information, will take a look today/tomorrow
I realize we really should have added a VVL regression test when acting the DRM change before, but back then I didn't have enough knowledge of DRM Format Modifier or a Mesa build to test with
Environment:
Describe the Issue
The new validation introduced in #7199 regressed the UB fix made in ce2c6ef and reintroduced the crashes in reported in #5649 and #5687 (though now it's now crashing during
vkBindImageMemory()
rather thanvkCreateImage()
). AFAICT, this regression was first released in v1.3.275 and persists today in v1.3.280.This happens because Mesa assumes that the pNext chain passed to
vkGetPhysicalDeviceImageFormatProperties2()
always includes includesVkPhysicalDeviceImageDrmFormatModifierInfoEXT
, which is a specification requirement perVUID-VkPhysicalDeviceImageFormatInfo2-tiling-02249
. The relevant Mesa code is here: https://gitlab.freedesktop.org/mesa/mesa/-/blob/24.0/src/intel/vulkan/anv_formats.c?ref_type=heads#L1239-1243Expected behavior
Per
VUID-VkPhysicalDeviceImageFormatInfo2-tiling-02249
:Valid Usage ID
Violation of
VUID-VkPhysicalDeviceImageFormatInfo2-tiling-02249
(unreported since the violation is in the validation layer itself)Additional context
GDB output
The text was updated successfully, but these errors were encountered: