Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp2448325ybt; Fri, 3 Jul 2020 09:16:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxsaGUzRpDVYy1++Xajzjami040/xrhVk1eQxJ9705XAyjUCmu3aMToxfs8iVkxElHUjjLp X-Received: by 2002:a17:906:841:: with SMTP id f1mr419094ejd.229.1593793006203; Fri, 03 Jul 2020 09:16:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1593793006; cv=none; d=google.com; s=arc-20160816; b=LfqSu/XoXmLwwpbY1wT2FVJAnA6JW3YwdXW2r+7EZiagLfAxjRTNmUz9pQApToTRRE 142bKcvvB5myCkaqBOP6u1tkwuBPSAR8lY5JU8x/3AM31/5Prx0UmHHLyeG4N655DAtb 2ZrO42dCFuMmEM/mhNh36NiKitmOEPowktnrT9w6Jfd5UzTEsj1BjcP737BONDUJcBHj AANin51niMTn4zdkksPITUL1c4Yn1ntvutD99eccRGB+i5E+bvCbyaZMQpsQAk05pDq2 inLATM1TRunLSvV5zWae7X6V0SjwfZRxNUUAboHxT9fQz9haXh27ERvPgc0y+ACeV8L7 uQrg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=9x0KnYFgOS8wTlKm8R3U+OuqdM4zspdu1o2f2BkBM4Q=; b=I2pV0Z4htBteWnqKLiTZPG7vB428XJDcKoYuO2G6Ch+qULb6haljIwMd3KM0bmh48Y zWL/r0qSa3sbHjrRGCoGqPlkyDNVLtryroI98RbMXk76S5IK4ok2r9Bs5E0o3H0+dhxy gwG6XDOpcnlqP7eygI5JiElByga3XWq+nSou9QyMG2bcOROPGMnsO5Gi1IGjdIr2FcKK oh0Ztc+E8fZL3yW9ONNI+2ckHBWmTg9zfUag2j20kW6pwJgMb7WkFxnuVbNmEL2CFhJz jSPdg81EDvhHP73B2szNLFArV+cGKxhOcxK6mB9Wbh+WKZ0+AuneQW5o9Ago2w2VJMwH xiEQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JyAyQVCl; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id h8si5553556ejj.516.2020.07.03.09.16.22; Fri, 03 Jul 2020 09:16:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JyAyQVCl; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726035AbgGCQQJ (ORCPT + 99 others); Fri, 3 Jul 2020 12:16:09 -0400 Received: from us-smtp-2.mimecast.com ([207.211.31.81]:23992 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726108AbgGCQQI (ORCPT ); Fri, 3 Jul 2020 12:16:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1593792967; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=9x0KnYFgOS8wTlKm8R3U+OuqdM4zspdu1o2f2BkBM4Q=; b=JyAyQVClUFjfnjp1TBEOPaHNz8sGxa35/tsx9+E6X3GY2CrAUYBWCBpq7GMqpzoUm73UU6 SzjXfB0eyeFCaEvfyUVGx7LERFSc8uOyCmDkMCp5vjEXu6wMf9SHjfrcUSk0J2QGiMfpf/ fvgIsh6ises5m+BJI0rle7zvGBEZoek= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-179-U1NQPhdUNraV5UCGBr5bMQ-1; Fri, 03 Jul 2020 12:16:05 -0400 X-MC-Unique: U1NQPhdUNraV5UCGBr5bMQ-1 Received: by mail-wm1-f72.google.com with SMTP id t145so35667376wmt.2 for ; Fri, 03 Jul 2020 09:16:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=9x0KnYFgOS8wTlKm8R3U+OuqdM4zspdu1o2f2BkBM4Q=; b=WbCK1hbUFDcZvJMDQF4Cf9kkxyXlhLF93RV3gfKeVK5z7zeG0MzIuVT4spks5vCc3P DsrqZ1pitslNc9BnlehktwUwkFQEJq/gX9hHx3ZK3tkVGW5Fki6xqwfrYhjj09UGCHbj buZ6ClQhGPm8EXdfSCXD/FrFcfD9OT5rOA8tvxAfNiwiDNrN3wfRroAnnO9E2EavxJ2C 9m9JSIXX51nwvApUXZObj5SNfwkfPat6YDGPWbY/i9dd+txy24J1lOkD+6JeuBe7EEmU 6+xOGVkbi4GL8YopoehLMYKcBSfku7u+fXQ0MFPHBYGzYzEw3wx+2/F0iS0xRVQ7xj/d rvrw== X-Gm-Message-State: AOAM533jeDOB8k3Q183xGVrT5bfkrA3JI7ZGISipKjquYKL42+HZIQiI itEeaYcR42iRwiRryjYHgxePLXw3PFu+JWNYuPFOkMlbLNUcCMqXuc6zHSWwT8+tpamCt2qX+G6 d2uJUtvW0IdU4uD90xF74Bkb8 X-Received: by 2002:a1c:6805:: with SMTP id d5mr36223283wmc.19.1593792964585; Fri, 03 Jul 2020 09:16:04 -0700 (PDT) X-Received: by 2002:a1c:6805:: with SMTP id d5mr36223255wmc.19.1593792964365; Fri, 03 Jul 2020 09:16:04 -0700 (PDT) Received: from ?IPv6:2001:b07:6468:f312:5cf9:fc14:deb7:51fc? ([2001:b07:6468:f312:5cf9:fc14:deb7:51fc]) by smtp.gmail.com with ESMTPSA id a3sm13510841wmb.7.2020.07.03.09.16.03 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 03 Jul 2020 09:16:03 -0700 (PDT) Subject: Re: [PATCH] KVM: x86: Inject #GP if guest attempts to toggle CR4.LA57 in 64-bit mode To: Sean Christopherson Cc: Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Sebastien Boeuf References: <20200703021714.5549-1-sean.j.christopherson@intel.com> From: Paolo Bonzini Message-ID: Date: Fri, 3 Jul 2020 18:16:03 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: <20200703021714.5549-1-sean.j.christopherson@intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/07/20 04:17, Sean Christopherson wrote: > Inject a #GP on MOV CR4 if CR4.LA57 is toggled in 64-bit mode, which is > illegal per Intel's SDM: > > CR4.LA57 > 57-bit linear addresses (bit 12 of CR4) ... blah blah blah ... > This bit cannot be modified in IA-32e mode. > > Note, the pseudocode for MOV CR doesn't call out the fault condition, > which is likely why the check was missed during initial development. > This is arguably an SDM bug and will hopefully be fixed in future > release of the SDM. > > Fixes: fd8cb433734ee ("KVM: MMU: Expose the LA57 feature to VM.") > Cc: stable@vger.kernel.org > Reported-by: Sebastien Boeuf > Signed-off-by: Sean Christopherson > --- > arch/x86/kvm/x86.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > index 00c88c2f34e4..2bb48896dbdc 100644 > --- a/arch/x86/kvm/x86.c > +++ b/arch/x86/kvm/x86.c > @@ -975,6 +975,8 @@ int kvm_set_cr4(struct kvm_vcpu *vcpu, unsigned long cr4) > if (is_long_mode(vcpu)) { > if (!(cr4 & X86_CR4_PAE)) > return 1; > + if ((cr4 ^ old_cr4) & X86_CR4_LA57) > + return 1; > } else if (is_paging(vcpu) && (cr4 & X86_CR4_PAE) > && ((cr4 ^ old_cr4) & pdptr_bits) > && !load_pdptrs(vcpu, vcpu->arch.walk_mmu, > Queued, thanks. Paolo