Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932959AbbLNXoJ (ORCPT ); Mon, 14 Dec 2015 18:44:09 -0500 Received: from www.sr71.net ([198.145.64.142]:59360 "EHLO blackbird.sr71.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932508AbbLNXoF (ORCPT ); Mon, 14 Dec 2015 18:44:05 -0500 Subject: Re: [PATCH 31/32] x86, pkeys: execute-only support To: Andy Lutomirski References: <20151214190542.39C4886D@viggo.jf.intel.com> <20151214190632.6A741188@viggo.jf.intel.com> <566F52CE.6080501@sr71.net> Cc: Kees Cook , LKML , Linux-MM , "x86@kernel.org" , Linus Torvalds , Andrew Morton , Dave Hansen From: Dave Hansen Message-ID: <566F5444.7000302@sr71.net> Date: Mon, 14 Dec 2015 15:44:04 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 827 Lines: 19 On 12/14/2015 03:39 PM, Andy Lutomirski wrote: >> > Nope. My linker-fu is weak. >> > >> > Can we even depend on the linker by itself? Even if the sections were >> > marked --x, we can't actually use them with those permissions unless we >> > have protection keys. >> > >> > Do we need some special tag on the section to tell the linker to map it >> > as --x under some conditions and r-x for others? >> > > Why? Wouldn't --x just end up acting like r-x if PKRU is absent? An app doing --x would expect it to be unreadable. I don't think we can just silently turn it in to r-x. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/