Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933926AbdGKVao (ORCPT ); Tue, 11 Jul 2017 17:30:44 -0400 Received: from gate.crashing.org ([63.228.1.57]:58022 "EHLO gate.crashing.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933883AbdGKVam (ORCPT ); Tue, 11 Jul 2017 17:30:42 -0400 Message-ID: <1499808577.2865.30.camel@kernel.crashing.org> Subject: Re: [RFC v5 12/38] mm: ability to disable execute permission on a key at creation From: Benjamin Herrenschmidt To: Dave Hansen , Ram Pai , linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org, linux-doc@vger.kernel.org, linux-kselftest@vger.kernel.org Cc: paulus@samba.org, mpe@ellerman.id.au, khandual@linux.vnet.ibm.com, aneesh.kumar@linux.vnet.ibm.com, bsingharora@gmail.com, hbabu@us.ibm.com, arnd@arndb.de, akpm@linux-foundation.org, corbet@lwn.net, mingo@redhat.com Date: Wed, 12 Jul 2017 07:29:37 +1000 In-Reply-To: <3bd2ffd4-33ad-ce23-3db1-d1292e69ca9b@intel.com> References: <1499289735-14220-1-git-send-email-linuxram@us.ibm.com> <1499289735-14220-13-git-send-email-linuxram@us.ibm.com> <3bd2ffd4-33ad-ce23-3db1-d1292e69ca9b@intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6 (3.22.6-2.fc25) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1003 Lines: 27 On Tue, 2017-07-11 at 11:11 -0700, Dave Hansen wrote: > On 07/05/2017 02:21 PM, Ram Pai wrote: > > Currently sys_pkey_create() provides the ability to disable read > > and write permission on the key, at creation. powerpc has the > > hardware support to disable execute on a pkey as well.This patch > > enhances the interface to let disable execute at key creation > > time. x86 does not allow this. Hence the next patch will add > > ability in x86 to return error if PKEY_DISABLE_EXECUTE is > > specified. That leads to the question... How do you tell userspace. (apologies if I missed that in an existing patch in the series) How do we inform userspace of the key capabilities ? There are at least two things userspace may want to know already: - What protection bits are supported for a key - How many keys exist - Which keys are available for use by userspace. On PowerPC, the kernel can reserve some keys for itself, so can the hypervisor. In fact, they do. Cheers, Ben.