Vulcan: blacklist cfi sanitize for calling Vulcan function pointers

Vulcan functions are loaded from shared library dynamically. Calling
those function pointer with cfi will cause SIGILL / ILL_ILLOPN.
So blacklist cfi sanitize for Vulcan function calls.

Bug: 1016885
Change-Id: I73989cebc9ab35d6f35fac508e8f0bcfc23cbd2e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2066937Reviewed-by: Peter Collingbourne <pcc@chromium.org>
Commit-Queue: Peng Huang <penghuang@chromium.org>
Cr-Commit-Position: refs/heads/master@{#743973}

tools/cfi/blacklist.txt

@@ -192,6 +192,15 @@ fun:*XImageDeleter*
 
 src:*mojo/public/c/system/thunks.cc
 
+# Call to vulkan function pointers from shared library.
+src:*/gpu/vulkan/*
+src:*components/viz/common/gpu/vulkan_in_process_context_provider.cc
+src:*gpu/command_buffer/service/skia_utils.cc
+src:*gpu/command_buffer/service/external_vk_*
+src:*components/viz/service/display_embedder/skia_output_device_vulkan.cc
+src:*/third_party/skia/src/gpu/vk/*
+src:*/third_party/skia/third_party/vulkanmemoryallocator/*
+
 # The follow entries are speculatively disabled. They're included in the
 # chromium build and include calls to dynamically resolved symbols; however,
 # they do not trigger cfi-icall failures in unit tests or normal chrome usage.