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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 21 Dec 2017 10:07:34 +0100 From: Paolo Bonzini <pbonzini@...hat.com> To: Lan Tianyu <tianyu.lan@...el.com>, Eric Biggers <ebiggers3@...il.com>, kvm@...r.kernel.org Cc: rkrcmar@...hat.com, christoffer.dall@...aro.org, x86@...nel.org, linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com, Eric Biggers <ebiggers@...gle.com>, Stephen Rothwell <sfr@...b.auug.org.au>, Linux-Next Mailing List <linux-next@...r.kernel.org> Subject: Re: [PATCH linux-next] KVM: x86: don't forget vcpu_put() in kvm_arch_vcpu_ioctl_set_sregs() On 21/12/2017 03:45, Lan Tianyu wrote: > Hi Paolo: > Should we check input sregs before loading vcpu? If input sregs is > invalid, the operation is redundant. That would be another way to fix the conflict. Note that the conflict is between two different trees (kvm/master and kvm/next), so in any case it will remain until the next merge window. Paolo
Powered by blists - more mailing lists