From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752740AbcGGOkk (ORCPT ); Thu, 7 Jul 2016 10:40:40 -0400 Received: from outbound-smtp09.blacknight.com ([46.22.139.14]:56538 "EHLO outbound-smtp09.blacknight.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751619AbcGGOkc (ORCPT ); Thu, 7 Jul 2016 10:40:32 -0400 Date: Thu, 7 Jul 2016 15:40:27 +0100 From: Mel Gorman To: Dave Hansen Cc: linux-kernel@vger.kernel.org, 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@linux.intel.com, arnd@arndb.de, hughd@google.com, viro@zeniv.linux.org.uk Subject: Re: [PATCH 1/9] x86, pkeys: add fault handling for PF_PK page fault bit Message-ID: <20160707144027.GX11498@techsingularity.net> References: <20160707124719.3F04C882@viggo.jf.intel.com> <20160707124720.6E0DC397@viggo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline In-Reply-To: <20160707124720.6E0DC397@viggo.jf.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 07, 2016 at 05:47:20AM -0700, Dave Hansen wrote: > > 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 An access fault gets propgated as SEGV_PKUERR. What happens if glibc does not recognise it? -- Mel Gorman SUSE Labs