From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f72.google.com (mail-pl0-f72.google.com [209.85.160.72]) by kanga.kvack.org (Postfix) with ESMTP id 18E5D6B000C for ; Mon, 26 Mar 2018 13:29:36 -0400 (EDT) Received: by mail-pl0-f72.google.com with SMTP id 30-v6so8657238ple.19 for ; Mon, 26 Mar 2018 10:29:36 -0700 (PDT) Received: from mga05.intel.com (mga05.intel.com. [192.55.52.43]) by mx.google.com with ESMTPS id b6-v6si6121888plm.202.2018.03.26.10.29.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Mar 2018 10:29:34 -0700 (PDT) Subject: [PATCH 0/9] [v2] x86, pkeys: two protection keys bug fixes From: Dave Hansen Date: Mon, 26 Mar 2018 10:27:21 -0700 Message-Id: <20180326172721.D5B2CBB4@viggo.jf.intel.com> Sender: owner-linux-mm@kvack.org List-ID: To: linux-kernel@vger.kernel.org Cc: linux-mm@kvack.org, Dave Hansen , linuxram@us.ibm.com, tglx@linutronix.de, dave.hansen@intel.com, mpe@ellerman.id.au, mingo@kernel.org, akpm@linux-foundation.org, shuah@kernel.org, shakeelb@google.com Changes from v1: * Added Fixes: and cc'd stable. No code changes. -- This fixes two bugs, and adds selftests to make sure they stay fixed: 1. pkey 0 was not usable via mprotect_pkey() because it had never been explicitly allocated. 2. mprotect(PROT_EXEC) memory could sometimes be left with the implicit exec-only protection key assigned. I already posted #1 previously. I'm including them both here because I don't think it's been picked up in case folks want to pull these all in a single bundle. Cc: Ram Pai Cc: Thomas Gleixner Cc: Dave Hansen Cc: Michael Ellermen Cc: Ingo Molnar Cc: Andrew Morton p Cc: Shuah Khan Cc: Shakeel Butt