From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933505AbcFIABX (ORCPT ); Wed, 8 Jun 2016 20:01:23 -0400 Received: from mga04.intel.com ([192.55.52.120]:16398 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932119AbcFIABU (ORCPT ); Wed, 8 Jun 2016 20:01:20 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,441,1459839600"; d="scan'208";a="118628955" Subject: [PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit To: linux-kernel@vger.kernel.org Cc: x86@kernel.org, linux-api@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org, torvalds@linux-foundation.org, akpm@linux-foundation.org, Dave Hansen , dave.hansen@linux.intel.com From: Dave Hansen Date: Wed, 08 Jun 2016 17:01:18 -0700 References: <20160609000117.71AC7623@viggo.jf.intel.com> In-Reply-To: <20160609000117.71AC7623@viggo.jf.intel.com> Message-Id: <20160609000118.0AAD5B0B@viggo.jf.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Dave Hansen PF_PK means that a memory access violated the protection key access restrictions. It is unconditionally an access_error() because the permissions set on the VMA don't matter (the PKRU value overrides it), and we never "resolve" PK faults (like how a COW can "resolve write fault). Signed-off-by: Dave Hansen --- b/arch/x86/mm/fault.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff -puN arch/x86/mm/fault.c~pkeys-105-add-pk-to-fault arch/x86/mm/fault.c --- a/arch/x86/mm/fault.c~pkeys-105-add-pk-to-fault 2016-06-08 16:26:33.253850287 -0700 +++ b/arch/x86/mm/fault.c 2016-06-08 16:26:33.259850559 -0700 @@ -1112,6 +1112,15 @@ access_error(unsigned long error_code, s { /* This is only called for the current mm, so: */ bool foreign = false; + + /* + * Read or write was blocked by protection keys. This is + * always an unconditional error and can never result in + * a follow-up action to resolve the fault, like a COW. + */ + if (error_code & PF_PK) + return 1; + /* * Make sure to check the VMA so that we do not perform * faults just to hit a PF_PK as soon as we fill in a _