From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1426712AbcBRUZQ (ORCPT ); Thu, 18 Feb 2016 15:25:16 -0500 Received: from terminus.zytor.com ([198.137.202.10]:47206 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1947059AbcBRUZK (ORCPT ); Thu, 18 Feb 2016 15:25:10 -0500 Date: Thu, 18 Feb 2016 12:24:04 -0800 From: tip-bot for Dave Hansen Message-ID: Cc: hpa@zytor.com, dvlasenk@redhat.com, riel@redhat.com, dave.hansen@linux.intel.com, dave@sr71.net, linux-kernel@vger.kernel.org, tglx@linutronix.de, peterz@infradead.org, bp@alien8.de, akpm@linux-foundation.org, mingo@kernel.org, luto@amacapital.net, brgerst@gmail.com, torvalds@linux-foundation.org Reply-To: dave.hansen@linux.intel.com, dave@sr71.net, riel@redhat.com, hpa@zytor.com, dvlasenk@redhat.com, torvalds@linux-foundation.org, brgerst@gmail.com, bp@alien8.de, akpm@linux-foundation.org, luto@amacapital.net, mingo@kernel.org, tglx@linutronix.de, peterz@infradead.org, linux-kernel@vger.kernel.org In-Reply-To: <20160212210225.BF0D4482@viggo.jf.intel.com> References: <20160212210225.BF0D4482@viggo.jf.intel.com> To: linux-tip-commits@vger.kernel.org Subject: [tip:mm/pkeys] x86/mm/pkeys: Dump PKRU with other kernel registers Git-Commit-ID: c0b17b5bd4b7b98e7c6b67c9f69343b64711271b X-Mailer: tip-git-log-daemon Robot-ID: Robot-Unsubscribe: Contact to get blacklisted from these emails MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Commit-ID: c0b17b5bd4b7b98e7c6b67c9f69343b64711271b Gitweb: http://git.kernel.org/tip/c0b17b5bd4b7b98e7c6b67c9f69343b64711271b Author: Dave Hansen AuthorDate: Fri, 12 Feb 2016 13:02:25 -0800 Committer: Ingo Molnar CommitDate: Thu, 18 Feb 2016 19:46:29 +0100 x86/mm/pkeys: Dump PKRU with other kernel registers Protection Keys never affect kernel mappings. But, they can affect whether the kernel will fault when it touches a user mapping. The kernel doesn't touch user mappings without some careful choreography and these accesses don't generally result in oopses. But, if one does, we definitely want to have PKRU available so we can figure out if protection keys played a role. Signed-off-by: Dave Hansen Reviewed-by: Thomas Gleixner Cc: Andrew Morton Cc: Andy Lutomirski Cc: Borislav Petkov Cc: Brian Gerst Cc: Dave Hansen Cc: Denys Vlasenko Cc: H. Peter Anvin Cc: Linus Torvalds Cc: Peter Zijlstra Cc: Rik van Riel Cc: linux-mm@kvack.org Link: http://lkml.kernel.org/r/20160212210225.BF0D4482@viggo.jf.intel.com Signed-off-by: Ingo Molnar --- arch/x86/kernel/process_64.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/x86/kernel/process_64.c b/arch/x86/kernel/process_64.c index b9d99e0..776229e 100644 --- a/arch/x86/kernel/process_64.c +++ b/arch/x86/kernel/process_64.c @@ -116,6 +116,8 @@ void __show_regs(struct pt_regs *regs, int all) printk(KERN_DEFAULT "DR0: %016lx DR1: %016lx DR2: %016lx\n", d0, d1, d2); printk(KERN_DEFAULT "DR3: %016lx DR6: %016lx DR7: %016lx\n", d3, d6, d7); + if (boot_cpu_has(X86_FEATURE_OSPKE)) + printk(KERN_DEFAULT "PKRU: %08x\n", read_pkru()); } void release_thread(struct task_struct *dead_task)