Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp6154886imd; Wed, 31 Oct 2018 07:37:32 -0700 (PDT) X-Google-Smtp-Source: AJdET5cyPMPZK+TfSf0UpryzGY++vGagkXTyd3cVd/iRw1U5vqX13MCm2117JueJmOmwvYcnGNb1 X-Received: by 2002:a17:902:3103:: with SMTP id w3-v6mr3777373plb.51.1540996652012; Wed, 31 Oct 2018 07:37:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540996651; cv=none; d=google.com; s=arc-20160816; b=RBbl0LjLTyAh/Sq9FpUlr1Sp9fdoHAa3QrdX006jn7oXtpUbwOegT5X6eF8f1NwYiJ jojCgEkPzh1uDwoUuQ0S1UMnhUgVDdBrnCRNIE512MuwP65SwczIuffPQaY7NMm5Y+6E 1cxBWP7uj01TvoE2zqZdSZS9GsWjsCJrEXuFpaZTDOcHHeykc/Ym7i4Bqi5eOk+uFkyq uCgg83Y8dtTB9sO0q8V14hAIpU72PiEESBY4YiE61seKIY7zBbsGmnzwfpYutOWE3miZ vgUbObrpcrSiI+5bop8HtTcq1d9bUGm/f/JLMLCIZCXx8Ml655YsuZ+RmjoVcJYlO1WQ 8l8w== 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; bh=BAEBI/TxJDMKHH6wzDb5J7igEokj9xRujShc6BDNpXM=; b=wBHgb8IwmcRJeMbetw3tVssZXUj5O2UsjOeqAbVdDzpu37aUuMIlBuEsoax+65G5Nz qwMd+XwvjIKNtoX6Vp87a2X8Wn9fcZGdOJjfL/JjDd8sgsYzPDHaq0nJwYS0acQrPwPb u4VzCHRCUGWbwxEnX0YVIfOh1xH5x84tA1xRvWKThdvXiTrXLVfFTuPZwX3EKCyWedq/ 2/dzSOB/wgz2WvZ/EJM0NL9v5KL4lN09bfBS6Fi0RyOTc13ef4IyXt8ufUisR/KnZ55l BuYVR5QrMeTUU1Dhspc77kder+ABkwaglSLWxdY8dKF/BWXMZOumULfr0zE4lJ3cqqSY khZg== 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 m17-v6si28840185pgj.155.2018.10.31.07.37.11; Wed, 31 Oct 2018 07:37:31 -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 S1729569AbeJaXfG (ORCPT + 99 others); Wed, 31 Oct 2018 19:35:06 -0400 Received: from foss.arm.com ([217.140.101.70]:41982 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729494AbeJaXfG (ORCPT ); Wed, 31 Oct 2018 19:35:06 -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 E67AB341; Wed, 31 Oct 2018 07:36:48 -0700 (PDT) Received: from localhost (e113682-lin.copenhagen.arm.com [10.32.144.41]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 4DB4F3F71D; Wed, 31 Oct 2018 07:36:48 -0700 (PDT) Date: Wed, 31 Oct 2018 15:36:46 +0100 From: Christoffer Dall To: Punit Agrawal Cc: kvmarm@lists.cs.columbia.edu, marc.zyngier@arm.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, suzuki.poulose@arm.com, stable@vger.kernel.org Subject: Re: [PATCH v8 1/9] KVM: arm/arm64: Ensure only THP is candidate for adjustment Message-ID: <20181031143646.GE12057@e113682-lin.lund.arm.com> References: <20181001155443.23032-1-punit.agrawal@arm.com> <20181001155443.23032-2-punit.agrawal@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181001155443.23032-2-punit.agrawal@arm.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 01, 2018 at 04:54:35PM +0100, Punit Agrawal wrote: > PageTransCompoundMap() returns true for hugetlbfs and THP > hugepages. This behaviour incorrectly leads to stage 2 faults for > unsupported hugepage sizes (e.g., 64K hugepage with 4K pages) to be > treated as THP faults. > > Tighten the check to filter out hugetlbfs pages. This also leads to > consistently mapping all unsupported hugepage sizes as PTE level > entries at stage 2. > > Signed-off-by: Punit Agrawal > Reviewed-by: Suzuki Poulose > Cc: Christoffer Dall > Cc: Marc Zyngier > Cc: stable@vger.kernel.org # v4.13+ Hmm, this function is only actually called from user_mem_abort() if we have (!hugetlb), so I'm not sure the cc stable here was actually warranted, nor that this patch is strictly necessary. It doesn't hurt, and makes the code potentially more robust for the future though. Am I missing something? Thanks, Christoffer > --- > virt/kvm/arm/mmu.c | 8 +++++++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/virt/kvm/arm/mmu.c b/virt/kvm/arm/mmu.c > index 7e477b3cae5b..c23a1b323aad 100644 > --- a/virt/kvm/arm/mmu.c > +++ b/virt/kvm/arm/mmu.c > @@ -1231,8 +1231,14 @@ static bool transparent_hugepage_adjust(kvm_pfn_t *pfnp, phys_addr_t *ipap) > { > kvm_pfn_t pfn = *pfnp; > gfn_t gfn = *ipap >> PAGE_SHIFT; > + struct page *page = pfn_to_page(pfn); > > - if (PageTransCompoundMap(pfn_to_page(pfn))) { > + /* > + * PageTransCompoungMap() returns true for THP and > + * hugetlbfs. Make sure the adjustment is done only for THP > + * pages. > + */ > + if (!PageHuge(page) && PageTransCompoundMap(page)) { > unsigned long mask; > /* > * The address we faulted on is backed by a transparent huge > -- > 2.18.0 >