The patch mentioned in comment #2 appears upstream in kernel version
5.6:
commit 763802b53a427ed3cbd419dbba255c414fdd9e7c
Author: Joerg Roedel <[email protected]>
Date: Sat Mar 21 18:22:41 2020 -0700
x86/mm: split vmalloc_sync_all()
It becomes an obvious problem for lttng in the kvm-kernel only because
lttng-modules creates two variants of wrappers for it depending on having
CONFIG_KALLSYMS set or not. If it is not set, then the wrapper just blindly
calls vmalloc_sync_all() in the hope that it has been exported. And that causes
the compile to fail.
However, even in the case of KALLSYMS being set, this will cause issues. Just
not at compile time. Because then the code looks up the address of
vmalloc_sync_all() at runtime and would then print a warning (on x86) about
possibly triggering recursive page faults.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874521
Title:
lttng-modules 2.10.8-1ubuntu2~18.04.1 ADT test failure with linux-kvm
4.15.0-1059.60
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1874521/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
