Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp536510pxb; Fri, 28 Jan 2022 04:52:58 -0800 (PST) X-Google-Smtp-Source: ABdhPJyezES/4B8dR4qczmy0Z/ZfXZWrirssJ1AliHEtfHRphD7wYZu+l1YCpR3jZwC8Sh77l5/2 X-Received: by 2002:a17:907:60ca:: with SMTP id hv10mr6801026ejc.134.1643374378351; Fri, 28 Jan 2022 04:52:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643374378; cv=none; d=google.com; s=arc-20160816; b=tI8MGeEIXJkDb49sh7EpwWEb5oPbz5b2+c2u2jRHQumW+4ae9S+mDSLf9LoAC9c8S0 vt5MVx/4nF+fTgLTwai0LQns3aAsOc3P9IuqPCa4HB1wD2z0JE5ZcABXbPiL07lkkRit 9woiElbIpR3gMa5ZFOVQREDox+U08aj/a7y8xP4JXRO/7odv3rcLzqS1XCKb6F5KPCMe Sn6PJBQQG+Oc8PREcw2yhWSeCS2mzxRv54PYfVxLKjWhhUtCtm3NOwe9+52z9MmLgyuk jQ10qzIt8ogeXz71+yYf2H+uMahqRLN8UdAgBg0sIs4XV6Md/FenahyuOaZRF+oHaJ3B 5ZtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=lkEVS+AXpzS0XHt4rjFIaywc+dRgzTTEPeG0KAcZClc=; b=NM3A7cgA8pkCCuprwl/izp7ocX1NgaIubCSKQ0r5VNFrBKaZwvJdVENZXlAf23oHq6 15BFY9HckhSkG7Wxs8ra9lLechcsy+xAtRztjUj64O0qnH5oiBCYcVPdPFC5vP5iKe/h yIOSVEIU8uC3n4QLrA+ND7x7ldWTOE5n2Z0KV9RG44l6SopwQZZCIZVgZxT+IVUIBk0j USromW4etoJFWeN5yg44Q0G2N1IIl2e4YweU5Zau1UL5Vxj0udG5Moy/vTYoaLEtU1VB G8oXbxJBhy8u8UIzMUjX004psI0P4etKz9yvV1QkmWlKkNNtK1MQRPA0wBmz71eIvsvi kO4g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b="OVD/Xmcz"; 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=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m29si2873547edb.470.2022.01.28.04.52.33; Fri, 28 Jan 2022 04:52:58 -0800 (PST) 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=@intel.com header.s=Intel header.b="OVD/Xmcz"; 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=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244922AbiA0Rz6 (ORCPT + 99 others); Thu, 27 Jan 2022 12:55:58 -0500 Received: from mga12.intel.com ([192.55.52.136]:65473 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244760AbiA0RzR (ORCPT ); Thu, 27 Jan 2022 12:55:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1643306117; x=1674842117; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=5N4sLTNdeUIAZnJLedt6mzC6DSo6VpBb9ZGGJjLgZSQ=; b=OVD/XmczWmbtmQFdtvmVK3ZfQ7WHS2LXFYewgwSnTgjuzQ+mY8NJteAI a36NEXztet5QS5Imp5Kvp9+eBUMOVXVCGKNKSmnT4KATW80n7aVtV8gZc nMrVSitj2dM6DOkU3tWKlR5UAseXvl/OBU26oH6uxwLXDPCiwRTX8Aahi WiVcDCKi4Y2945jTVHwShcU9dZJedX4r9qqjR1WnQvLq8aXNQd134LsoR 03e+dc9cu4pHBNbe9GIGfEiHsKjX5Cj8HIv3/WnI/3REFJwef5kCqhwrj 3umbJ685QLh/brpckS6DrcjBbt1G/ggzk81EaD/cnhu33mTPar9Kfovsq g==; X-IronPort-AV: E=McAfee;i="6200,9189,10239"; a="226899123" X-IronPort-AV: E=Sophos;i="5.88,321,1635231600"; d="scan'208";a="226899123" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Jan 2022 09:55:08 -0800 X-IronPort-AV: E=Sophos;i="5.88,321,1635231600"; d="scan'208";a="674796070" Received: from iweiny-desk2.sc.intel.com (HELO localhost) ([10.3.52.147]) by fmsmga001-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 27 Jan 2022 09:55:08 -0800 From: ira.weiny@intel.com To: Dave Hansen , "H. Peter Anvin" , Dan Williams Cc: Ira Weiny , Fenghua Yu , Rick Edgecombe , linux-kernel@vger.kernel.org Subject: [PATCH V8 08/44] x86/fault: Adjust WARN_ON for PKey fault Date: Thu, 27 Jan 2022 09:54:29 -0800 Message-Id: <20220127175505.851391-9-ira.weiny@intel.com> X-Mailer: git-send-email 2.31.1 In-Reply-To: <20220127175505.851391-1-ira.weiny@intel.com> References: <20220127175505.851391-1-ira.weiny@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Ira Weiny Previously if a Protection key fault occurred it indicated something very wrong because user page mappings are not supposed to be in the kernel address space. Now PKey faults may happen on kernel mappings if the feature is enabled. If PKS is enabled, avoid the warning in the fault path. Cc: Sean Christopherson Cc: Dan Williams Signed-off-by: Ira Weiny --- arch/x86/mm/fault.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c index d0074c6ed31a..6ed91b632eac 100644 --- a/arch/x86/mm/fault.c +++ b/arch/x86/mm/fault.c @@ -1148,11 +1148,15 @@ do_kern_addr_fault(struct pt_regs *regs, unsigned long hw_error_code, unsigned long address) { /* - * Protection keys exceptions only happen on user pages. We - * have no user pages in the kernel portion of the address - * space, so do not expect them here. + * X86_PF_PK (Protection key exceptions) may occur on kernel addresses + * when PKS (PKeys Supervisor) is enabled. + * + * However, if PKS is not enabled WARN if this exception is seen + * because there are no user pages in the kernel portion of the address + * space. */ - WARN_ON_ONCE(hw_error_code & X86_PF_PK); + WARN_ON_ONCE(!cpu_feature_enabled(X86_FEATURE_PKS) && + (hw_error_code & X86_PF_PK)); #ifdef CONFIG_X86_32 /* -- 2.31.1