Received: by 10.192.165.148 with SMTP id m20csp508775imm; Fri, 27 Apr 2018 02:53:30 -0700 (PDT) X-Google-Smtp-Source: AB8JxZq8JyfVbbPggt3oN9GtQFBtwElfrgsyo7xa7CJ7ElV1HM5r2ypZu3lyw3Svj2H/DitH1C2e X-Received: by 2002:a65:4dc7:: with SMTP id q7-v6mr1558535pgt.305.1524822809972; Fri, 27 Apr 2018 02:53:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524822809; cv=none; d=google.com; s=arc-20160816; b=sAeZxRqA/CN31SWBoAwAXAynmZ6HNg47TqdwAadpQdBnJNVhLLe9SHvfNuuXsgIipn teuwEZ3maT9qLcnHWAp6135/EI9rrrYYVyeaitpRkKuQWSmmocxYy7zH3vHCdIGx+eFD RuhwN8k3dnKj6vzf90Z+OufRYrsfoH/6Ad1nEBg4wn42/bR87hvCxtZ4sO6QSXxLM9Yg kdlrDxkPHZ7IsREAdzsxPpqLogV1RVxHTz2qQb0mlSCLZwsC2a6dOI0KF5vSzd/uGwWf kwCGmbnCAeBN6Ws7o3WjmhtK0L7aUEQbwkjy+N+ejjDTX9UIGJhV/9rNREBIPdOtNKFQ yh3g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=xxRwqHj1P+S29njjKmWhbYji13mBgHwZs60kzK5unZg=; b=O3cgE5hUWgz1K+oxZlKMjFvXExnXNUIja3ZqIicn+NFBtnOo8FPdb+MyzBZObSI7Rg ENlnk5MSaUeseDRAcyS2c5FjHjuTlLuEhm0Vb45pt2DIo6nWj8lgUMJkbDQN5GZCf8pH lj+lQHj68MVvJVc/IVzty2GNlnUbbsFxtvjUFBDMS7XYOzofGDQOzV+jZ14aNCkDAuTr /ZeFsPTldSEljqS/4oWK40/W/t5eNtZVKrFCq7LE61m2X2fr7JQifde94UHcfDtgRtSX xjrTBNXbzpFSeN9MNVwD+D/8hEx8KaLnJP9kikpD0YQUWfvVOVgf/n4zvWLwQ1wTvqwr dUPQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b4-v6si925179pgu.79.2018.04.27.02.53.16; Fri, 27 Apr 2018 02:53:29 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932613AbeD0JwC (ORCPT + 99 others); Fri, 27 Apr 2018 05:52:02 -0400 Received: from usa-sjc-mx-foss1.foss.arm.com ([217.140.101.70]:37616 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757753AbeD0JwB (ORCPT ); Fri, 27 Apr 2018 05:52:01 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 03C4715AD; Fri, 27 Apr 2018 02:52:01 -0700 (PDT) Received: from localhost (unknown [10.37.9.163]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 646833F487; Fri, 27 Apr 2018 02:52:00 -0700 (PDT) Date: Fri, 27 Apr 2018 11:51:58 +0200 From: Christoffer Dall To: Mark Rutland Cc: linux-arm-kernel@lists.infradead.org, linux-arch@vger.kernel.org, arnd@arndb.de, marc.zyngier@arm.com, catalin.marinas@arm.com, awallis@codeaurora.org, kernel-hardening@lists.openwall.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, ramana.radhakrishnan@arm.com, kvmarm@lists.cs.columbia.edu Subject: Re: [PATCHv3 03/11] arm64/kvm: hide ptrauth from guests Message-ID: <20180427095158.GI13249@C02W217FHV2R.local> References: <20180417183735.56985-1-mark.rutland@arm.com> <20180417183735.56985-4-mark.rutland@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180417183735.56985-4-mark.rutland@arm.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Apr 17, 2018 at 07:37:27PM +0100, Mark Rutland wrote: > In subsequent patches we're going to expose ptrauth to the host kernel > and userspace, but things are a bit trickier for guest kernels. For the > time being, let's hide ptrauth from KVM guests. > > Regardless of how well-behaved the guest kernel is, guest userspace > could attempt to use ptrauth instructions, triggering a trap to EL2, > resulting in noise from kvm_handle_unknown_ec(). So let's write up a > handler for the PAC trap, which silently injects an UNDEF into the > guest, as if the feature were really missing. > > Signed-off-by: Mark Rutland > Cc: Christoffer Dall > Cc: Marc Zyngier > Cc: kvmarm@lists.cs.columbia.edu > --- > arch/arm64/kvm/handle_exit.c | 18 ++++++++++++++++++ > arch/arm64/kvm/sys_regs.c | 9 +++++++++ > 2 files changed, 27 insertions(+) > > diff --git a/arch/arm64/kvm/handle_exit.c b/arch/arm64/kvm/handle_exit.c > index e5e741bfffe1..5114ad691eae 100644 > --- a/arch/arm64/kvm/handle_exit.c > +++ b/arch/arm64/kvm/handle_exit.c > @@ -173,6 +173,23 @@ static int handle_sve(struct kvm_vcpu *vcpu, struct kvm_run *run) > return 1; > } > > +/* > + * Guest usage of a ptrauth instruction (which the guest EL1 did not turn into > + * a NOP), or guest EL1 access to a ptrauth register. > + */ > +static int kvm_handle_ptrauth(struct kvm_vcpu *vcpu, struct kvm_run *run) > +{ > + /* > + * We don't currently suport ptrauth in a guest, and we mask the ID > + * registers to prevent well-behaved guests from trying to make use of > + * it. > + * > + * Inject an UNDEF, as if the feature really isn't present. > + */ > + kvm_inject_undefined(vcpu); > + return 1; > +} > + > static exit_handle_fn arm_exit_handlers[] = { > [0 ... ESR_ELx_EC_MAX] = kvm_handle_unknown_ec, > [ESR_ELx_EC_WFx] = kvm_handle_wfx, > @@ -195,6 +212,7 @@ static exit_handle_fn arm_exit_handlers[] = { > [ESR_ELx_EC_BKPT32] = kvm_handle_guest_debug, > [ESR_ELx_EC_BRK64] = kvm_handle_guest_debug, > [ESR_ELx_EC_FP_ASIMD] = handle_no_fpsimd, > + [ESR_ELx_EC_PAC] = kvm_handle_ptrauth, > }; > > static exit_handle_fn kvm_get_exit_handler(struct kvm_vcpu *vcpu) > diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c > index 806b0b126a64..eee399c35e84 100644 > --- a/arch/arm64/kvm/sys_regs.c > +++ b/arch/arm64/kvm/sys_regs.c > @@ -1000,6 +1000,15 @@ static u64 read_id_reg(struct sys_reg_desc const *r, bool raz) > task_pid_nr(current)); > > val &= ~(0xfUL << ID_AA64PFR0_SVE_SHIFT); > + } else if (id == SYS_ID_AA64ISAR1_EL1) { > + const u64 ptrauth_mask = (0xfUL << ID_AA64ISAR1_APA_SHIFT) | > + (0xfUL << ID_AA64ISAR1_API_SHIFT) | > + (0xfUL << ID_AA64ISAR1_GPA_SHIFT) | > + (0xfUL << ID_AA64ISAR1_GPI_SHIFT); > + if (val & ptrauth_mask) > + pr_err_once("kvm [%i]: ptrauth unsupported for guests, suppressing\n", > + task_pid_nr(current)); > + val &= ~ptrauth_mask; > } else if (id == SYS_ID_AA64MMFR1_EL1) { > if (val & (0xfUL << ID_AA64MMFR1_LOR_SHIFT)) > pr_err_once("kvm [%i]: LORegions unsupported for guests, suppressing\n", > -- > 2.11.0 > With the change to the debugging print: Reviewed-by: Christoffer Dall