Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751937AbbLHSmn (ORCPT ); Tue, 8 Dec 2015 13:42:43 -0500 Received: from www.linutronix.de ([62.245.132.108]:51787 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751219AbbLHSmm (ORCPT ); Tue, 8 Dec 2015 13:42:42 -0500 Date: Tue, 8 Dec 2015 19:41:53 +0100 (CET) From: Thomas Gleixner To: Dave Hansen cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, x86@kernel.org, dave.hansen@linux.intel.com Subject: Re: [PATCH 27/34] x86, pkeys: make mprotect_key() mask off additional vm_flags In-Reply-To: <20151204011502.251A0E5B@viggo.jf.intel.com> Message-ID: References: <20151204011424.8A36E365@viggo.jf.intel.com> <20151204011502.251A0E5B@viggo.jf.intel.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001,URIBL_BLOCKED=0.001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1358 Lines: 37 On Thu, 3 Dec 2015, Dave Hansen wrote: > > From: Dave Hansen > > Today, mprotect() takes 4 bits of data: PROT_READ/WRITE/EXEC/NONE. > Three of those bits: READ/WRITE/EXEC get translated directly in to > vma->vm_flags by calc_vm_prot_bits(). If a bit is unset in > mprotect()'s 'prot' argument then it must be cleared in vma->vm_flags > during the mprotect() call. > > We do the by first calculating the VMA flags we want set, then > clearing the ones we do not want to inherit from the original VMA: > > vm_flags = calc_vm_prot_bits(prot, key); > ... > newflags = vm_flags; > newflags |= (vma->vm_flags & ~(VM_READ | VM_WRITE | VM_EXEC)); > > However, we *also* want to mask off the original VMA's vm_flags in > which we store the protection key. > > To do that, this patch adds a new macro: > > ARCH_VM_FLAGS_AFFECTED_BY_MPROTECT -ENOSUCHMACRO > which allows the architecture to specify additional bits that it would > like cleared. We use that to ensure that the VM_PKEY_BIT* bits get > cleared. Other than that: Reviewed-by: Thomas Gleixner -- 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/