layers: thread checks of VkCommandBuffer pool read

Object reads of VkCommandBuffer should also be reads of their pool.
A single thread may have multiple uses of a pool in one call.
That will be allowed because the uses are all in a single thread.

1 files changed, 4 insertions, 8 deletions

diff --git a/layers/threading.h b/layers/threading.h
index 23d44c2d..0b8e947d 100644
--- a/layers/threading.h
+++ b/layers/threading.h
@@ -324,18 +324,14 @@ static void finishWriteObject(struct layer_data *my_data, VkCommandBuffer object
         finishWriteObject(my_data, command_pool_map[object]);
     }
 }
-static void startReadObject(struct layer_data *my_data, VkCommandBuffer object, bool lockPool=false)
+static void startReadObject(struct layer_data *my_data, VkCommandBuffer object)
 {
-    if (lockPool) {
-        startReadObject(my_data, command_pool_map[object]);
-    }
+    startReadObject(my_data, command_pool_map[object]);
     my_data->c_VkCommandBuffer.startRead(my_data->report_data, object);
 }
-static void finishReadObject(struct layer_data *my_data, VkCommandBuffer object, bool lockPool=false)
+static void finishReadObject(struct layer_data *my_data, VkCommandBuffer object)
 {
     my_data->c_VkCommandBuffer.finishRead(object);
-    if (lockPool) {
-        finishReadObject(my_data, command_pool_map[object]);
-    }
+    finishReadObject(my_data, command_pool_map[object]);
 }
 #endif // THREADING_H