fix: vmalloc on v5.8 without KALLSYMS
authorMichael Jeanson <mjeanson@efficios.com>
Tue, 7 Jul 2020 15:15:39 +0000 (11:15 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Tue, 7 Jul 2020 20:30:10 +0000 (16:30 -0400)
Signed-off-by: Michael Jeanson <mjeanson@efficios.com>
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Change-Id: Ic945dad92e78a5bc2895a969a10c527e1349decf

include/wrapper/vmalloc.h

index 596fb9ed11a0885f3d9c388398dd607f1ec28ea1..f742f48f9b44767119045427ff07a28357af6cba 100644 (file)
@@ -117,9 +117,19 @@ void __canary__vmalloc_sync_all(void)
 
 #endif /* #else #if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,6,0)) */
 
-#else
+#else /* CONFIG_KALLSYMS */
+
+#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,8,0))
+
+/*
+ * wrapper_vmalloc_sync_mappings was removed in v5.8, the vmalloc mappings
+ * are now synchronized when they are created or torn down.
+ */
+static inline
+void wrapper_vmalloc_sync_mappings(void)
+{}
 
-#if (LINUX_VERSION_CODE >= KERNEL_VERSION(5,6,0) \
+#elif (LINUX_VERSION_CODE >= KERNEL_VERSION(5,6,0) \
   || LTTNG_KERNEL_RANGE(5,5,12, 5,6,0)            \
   || LTTNG_KERNEL_RANGE(5,4,28, 5,5,0)            \
   || LTTNG_KERNEL_RANGE(5,2,37, 5,3,0)            \
This page took 0.026971 seconds and 4 git commands to generate.