Closed Wenzel closed 7 years ago
So i found a solution by disabling every call to debugfs in kvm/virt/kvm_main.c
For an unknown reason, the config option CONFIG_KVM_DEBUG_FS
is available in the kernel, but never used anywhere in the code.
the call to debugfs_* function in the kvm code are mandatory.
The solution was to make these calls optional. See this commit which fixes the problem: really disable KVM debug fs if CONFIG_KVM_DEBUG_FS is unset
Currently, the branch
linux-vmi
is based on the latest stable linux kernelv4.9
.However running nitro on this kernel causes the kernel to crash because of a
kernel NULL pointer dereference
, triggered at the end of the execution.The stack trace shown in
dmesg
is the following:The problem comes from the new
KVM_DEBUG_FS
feature, which was absent of the latest stable kernel for nitro (v4.5.x
)This is the
debugfs_remove_recursive
function:And apparently, during a call to
inode_lock
, it makes a call todown_write
with a bad pointerOf course, this problem appears only at the end of a nitro run, be it when
main.py
ortest_nitro.py
calls theirat_exit
cleanup.One thing that troubles me is that i check my kernel configuration, and the symbol
KVM_DEBUG_FS
was not enabledN
...Any ideas ?