From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Borntraeger Subject: Re: [PATCH 3/3] kvm-s390: provide standard guest registers via kvm_run Date: Wed, 04 Jan 2012 09:30:23 +0100 Message-ID: <4F040E1F.6050806@de.ibm.com> References: <20111222115646.248800653@de.ibm.com> <1325605858-30492-1-git-send-email-borntraeger@de.ibm.com> <1325605858-30492-4-git-send-email-borntraeger@de.ibm.com> <20120104081646.GA2522@osiris.boeblingen.de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Avi Kivity , Marcelo Tossati , Carsten Otte , Alexander Graf , Jens Freimann , Cornelia Huck , Martin Schwidefsky , KVM To: Heiko Carstens Return-path: Received: from e06smtp11.uk.ibm.com ([195.75.94.107]:53222 "EHLO e06smtp11.uk.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752936Ab2ADIay (ORCPT ); Wed, 4 Jan 2012 03:30:54 -0500 Received: from /spool/local by e06smtp11.uk.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 4 Jan 2012 08:30:48 -0000 Received: from d06av11.portsmouth.uk.ibm.com (d06av11.portsmouth.uk.ibm.com [9.149.37.252]) by d06nrmr1307.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q048UjQd1908760 for ; Wed, 4 Jan 2012 08:30:45 GMT Received: from d06av11.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av11.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q048Ui3H002232 for ; Wed, 4 Jan 2012 01:30:45 -0700 In-Reply-To: <20120104081646.GA2522@osiris.boeblingen.de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 04/01/12 09:16, Heiko Carstens wrote: >> save_fp_regs(&vcpu->arch.host_fpregs); >> save_access_regs(vcpu->arch.host_acrs); >> - vcpu->arch.guest_fpregs.fpc &= FPC_VALID_MASK; >> - restore_fp_regs(&vcpu->arch.guest_fpregs); >> - restore_access_regs(vcpu->arch.guest_acrs); >> + vcpu->run->sync_rw.fpregs.fpc &= FPC_VALID_MASK; >> + restore_fp_regs(&vcpu->run->sync_rw.fpregs); > > ...this is broken, since userspace can update the floating point control > register contents after the kernel has masked out the offending bits but > before the register is actually loaded. > Which in turn could cause a kernel crash, hm? Indeed, I need to fix that. Thanks for spotting. I will respin patch 2 and 3 as soon as the interface in patch 1 is settled. Christian