Jan spotted that we shouldn't use a function only available when CONFIG_COMPAT
in a struct that's available without the config option.
So since my patch introduces that, let's just not export the compat ioctl
function when CONFIG_COMPAT is not set, so we don't break then.
Reported-by: Jan Kiszka <jan.kis...@siemens.com>
Signed-off-by: Alexander Graf <ag...@suse.de>
---
virt/kvm/kvm_main.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c
index 54a272f..bd44fb4 100644
--- a/virt/kvm/kvm_main.c
+++ b/virt/kvm/kvm_main.c
@@ -1623,7 +1623,9 @@ static int kvm_vm_mmap(struct file *file, struct
vm_area_struct *vma)
static struct file_operations kvm_vm_fops = {
.release = kvm_vm_release,
.unlocked_ioctl = kvm_vm_ioctl,
+#ifdef CONFIG_COMPAT
.compat_ioctl = kvm_vm_compat_ioctl,
+#endif
.mmap = kvm_vm_mmap,
};
--
1.6.0.2
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
