From 7276191d5944b4c3d5a272a4a07274933fac4346 Mon Sep 17 00:00:00 2001 From: "Thomas H.P. Andersen" Date: Sun, 23 Feb 2025 15:07:50 +0100 Subject: [PATCH] nvk: use a valid allocation scope VK_OBJECT_TYPE_DESCRIPTOR_POOL is used in vk_zalloc2 as allocation scope. This should probably have been object scope. Fixes: 607686f6bfb17d03d3ba77eddbb3c28fbd080d99 Part-of: --- src/nouveau/vulkan/nvk_descriptor_set.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/nouveau/vulkan/nvk_descriptor_set.c b/src/nouveau/vulkan/nvk_descriptor_set.c index 9731302b602..4fcb9f7d7e3 100644 --- a/src/nouveau/vulkan/nvk_descriptor_set.c +++ b/src/nouveau/vulkan/nvk_descriptor_set.c @@ -611,7 +611,7 @@ nvk_CreateDescriptorPool(VkDevice _device, if (mem_size > 0) { if (pCreateInfo->flags & VK_DESCRIPTOR_POOL_CREATE_HOST_ONLY_BIT_EXT) { pool->host_mem = vk_zalloc2(&dev->vk.alloc, pAllocator, mem_size, - 16, VK_OBJECT_TYPE_DESCRIPTOR_POOL); + 16, VK_SYSTEM_ALLOCATION_SCOPE_OBJECT); if (pool->host_mem == NULL) { nvk_destroy_descriptor_pool(dev, pAllocator, pool); return vk_error(dev, VK_ERROR_OUT_OF_HOST_MEMORY);