lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANRm+Cy2enkDmbb8fs6Kt2Jyd1_CsGsGy1jqJjRUbH_Fgve79w@mail.gmail.com>
Date:	Sun, 5 Jun 2016 07:55:46 +0800
From:	Wanpeng Li <kernellwp@...il.com>
To:	Paolo Bonzini <pbonzini@...hat.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	kvm <kvm@...r.kernel.org>, Radim Krcmar <rkrcmar@...hat.com>
Subject: Re: [PATCH 5/7] KVM: x86: avoid vmalloc(0) in the KVM_SET_CPUID

2016-06-01 20:09 GMT+08:00 Paolo Bonzini <pbonzini@...hat.com>:
> This causes an ugly dmesg splat.  Beautified syzkaller testcase:
>
>     #include <unistd.h>
>     #include <sys/syscall.h>
>     #include <sys/ioctl.h>
>     #include <fcntl.h>
>     #include <linux/kvm.h>
>
>     long r[8];
>
>     int main()
>     {
>         struct kvm_irq_routing ir = { 0 };
>         r[2] = open("/dev/kvm", O_RDWR);
>         r[3] = ioctl(r[2], KVM_CREATE_VM, 0);
>         r[4] = ioctl(r[3], KVM_SET_GSI_ROUTING, &ir);
>         return 0;
>     }
>

The patch subject is not correct.

Regards,
Wanpeng Li

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ