KVM: Return -ENOTTY on unrecognized ioctls

Not the incorrect -EINVAL.

Signed-off-by: Avi Kivity <avi@redhat.com>
This commit is contained in:
Avi Kivity 2009-08-26 14:57:07 +03:00
parent 680b3648ba
commit 367e1319b2
4 changed files with 4 additions and 4 deletions

View File

@ -941,7 +941,7 @@ long kvm_arch_vm_ioctl(struct file *filp,
{ {
struct kvm *kvm = filp->private_data; struct kvm *kvm = filp->private_data;
void __user *argp = (void __user *)arg; void __user *argp = (void __user *)arg;
int r = -EINVAL; int r = -ENOTTY;
switch (ioctl) { switch (ioctl) {
case KVM_SET_MEMORY_REGION: { case KVM_SET_MEMORY_REGION: {

View File

@ -421,7 +421,7 @@ long kvm_arch_vm_ioctl(struct file *filp,
switch (ioctl) { switch (ioctl) {
default: default:
r = -EINVAL; r = -ENOTTY;
} }
return r; return r;

View File

@ -150,7 +150,7 @@ long kvm_arch_vm_ioctl(struct file *filp,
break; break;
} }
default: default:
r = -EINVAL; r = -ENOTTY;
} }
return r; return r;

View File

@ -2176,7 +2176,7 @@ long kvm_arch_vm_ioctl(struct file *filp,
{ {
struct kvm *kvm = filp->private_data; struct kvm *kvm = filp->private_data;
void __user *argp = (void __user *)arg; void __user *argp = (void __user *)arg;
int r = -EINVAL; int r = -ENOTTY;
/* /*
* This union makes it completely explicit to gcc-3.x * This union makes it completely explicit to gcc-3.x
* that these two variables' stack usage should be * that these two variables' stack usage should be