From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932572AbeCLPqH (ORCPT ); Mon, 12 Mar 2018 11:46:07 -0400 Received: from mga07.intel.com ([134.134.136.100]:62950 "EHLO mga07.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932513AbeCLPqG (ORCPT ); Mon, 12 Mar 2018 11:46:06 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,462,1515484800"; d="scan'208";a="24521645" Subject: Re: [PATCH] x86, powerpc : pkey-mprotect must allow pkey-0 To: Ram Pai , Michael Ellerman References: <1520583161-11741-1-git-send-email-linuxram@us.ibm.com> <87lgf1v9di.fsf@concordia.ellerman.id.au> <20180309200631.GS1060@ram.oc3035372033.ibm.com> Cc: mingo@redhat.com, akpm@linux-foundation.org, linuxppc-dev@lists.ozlabs.org, linux-mm@kvack.org, x86@kernel.org, linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org, benh@kernel.crashing.org, paulus@samba.org, khandual@linux.vnet.ibm.com, aneesh.kumar@linux.vnet.ibm.com, bsingharora@gmail.com, hbabu@us.ibm.com, mhocko@kernel.org, bauerman@linux.vnet.ibm.com, ebiederm@xmission.com, corbet@lwn.net, arnd@arndb.de, fweimer@redhat.com, msuchanek@suse.com, Ulrich.Weigand@de.ibm.com From: Dave Hansen Message-ID: <96b08909-906b-86b6-f4ee-67b9f8eff5d7@intel.com> Date: Mon, 12 Mar 2018 08:46:04 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180309200631.GS1060@ram.oc3035372033.ibm.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/09/2018 12:06 PM, Ram Pai wrote: > On Fri, Mar 09, 2018 at 09:19:53PM +1100, Michael Ellerman wrote: >> Ram Pai writes: >> >>> Once an address range is associated with an allocated pkey, it cannot be >>> reverted back to key-0. There is no valid reason for the above behavior. On >>> the contrary applications need the ability to do so. >> Please explain this in much more detail. Is it an ABI change? > Not necessarily an ABI change. older binary applications will continue > to work. It can be considered as a bug-fix. Yeah, agreed. I do not think this is an ABI change.