Received: by 10.213.65.68 with SMTP id h4csp645087imn; Fri, 23 Mar 2018 12:24:17 -0700 (PDT) X-Google-Smtp-Source: AG47ELtBk1a+HZPs6gg+7P2ZBvxP9fHxyNSpO522vCbNegi472w5N8tf+0Dqem8Aiimu0M3krI0w X-Received: by 2002:a17:902:2f81:: with SMTP id t1-v6mr30727628plb.290.1521833057098; Fri, 23 Mar 2018 12:24:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521833057; cv=none; d=google.com; s=arc-20160816; b=GvfTE121TAPEUWIkDiCWY0YR64v+UbPppTFYipRC9jiNWtWeLcfcU9ZyYkGYmm/U5G 6bSJH8O97c0KGnoVEqqK0GuUz3YIRjXrzQ4iLLLqBYa8CVeEE/iPcNEWJu0OJhS2dZQV qq6O6H/5JQvN0WKZyMAEMbbmkvfgkNyszjVBiIPP7zlEE5iovsj1lqARCAG4OL8HyNdr i4/wP+rfVVsWAultLRMqy495qo6evxvNedixxnFIL+J3GD6Z0gx+dgsKFT+Yu5wY70V5 HJxnGtsfaLb2e5dWEolqO1wlHhzQ7LZtKxXGW9OxmGswjRFdpV3alroJtR+r4K+D6eX7 +ZzA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:cc:references:to:subject:arc-authentication-results; bh=WxA4vfZulYmU+SQ6zRW6LVfOfyTJiOdFveYVHIqhaSI=; b=jWLTy0CArCu3sIpdu5j+3RRqFVQnxstP/qI3rnnz7LPaFb8zdE/UzGbusX1cuWk+oX zS18y6JUAPpiuKkC4NiE0nVLiyODORXe8OfAy9BggCggXKCKm7FD9ZUxF+uljNo0Hzqo nS4Iyv/Dua726cy8UCbH7XxN0r373Gv7CaGKbXeD2jlKTegfqUGuqIYW2Jj7gpxit0Vq q7sO1oPsMWsLxE43nyR4iZXSkR/exO0TE9YzClLkPLzJR3xXOqtMdrDZGh0P9+jZLDPP ePzXD65e3xo0DcwxYrBBaAVnJkMtNFANoNBA4pf6JFy32RuLq+WCFMuQJQFuhoJ88Ri7 5MDQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f3-v6si9952076plm.433.2018.03.23.12.24.02; Fri, 23 Mar 2018 12:24:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752447AbeCWTXF (ORCPT + 99 others); Fri, 23 Mar 2018 15:23:05 -0400 Received: from mga04.intel.com ([192.55.52.120]:16349 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751983AbeCWTXE (ORCPT ); Fri, 23 Mar 2018 15:23:04 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Mar 2018 12:23:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,351,1517904000"; d="scan'208";a="185454733" Received: from ray.jf.intel.com (HELO [10.7.201.126]) ([10.7.201.126]) by orsmga004.jf.intel.com with ESMTP; 23 Mar 2018 12:23:04 -0700 Subject: Re: [PATCH 4/9] x86, pkeys: override pkey when moving away from PROT_EXEC To: Shakeel Butt , Dave Hansen References: <20180323180903.33B17168@viggo.jf.intel.com> <20180323180911.E43ACAB8@viggo.jf.intel.com> Cc: LKML , Linux MM , linuxram@us.ibm.com, Thomas Gleixner , mpe@ellerman.id.au, Ingo Molnar , Andrew Morton , shuah@kernel.org From: Dave Hansen Message-ID: Date: Fri, 23 Mar 2018 12:23:02 -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: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/23/2018 12:15 PM, Shakeel Butt wrote: >> We had a check for PROT_READ/WRITE, but it did not work >> for PROT_NONE. This entirely removes the PROT_* checks, >> which ensures that PROT_NONE now works. >> >> Reported-by: Shakeel Butt >> Signed-off-by: Dave Hansen > Should there be a 'Fixes' tag? Also should this patch go to stable? There could be, but I'm to lazy to dig up the original commit. Does it matter? And, yes, I think it probably makes sense for -stable. I'll add that if I resend this series.