From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752846AbbCZSdr (ORCPT ); Thu, 26 Mar 2015 14:33:47 -0400 Received: from mga11.intel.com ([192.55.52.93]:42654 "EHLO mga11.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751402AbbCZSdg (ORCPT ); Thu, 26 Mar 2015 14:33:36 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,474,1422950400"; d="scan'208";a="546857786" Subject: [PATCH 11/17] x86, mpx: we do not allocate the bounds directory To: linux-kernel@vger.kernel.org Cc: x86@kernel.org, tglx@linutronix.de, Dave Hansen , dave.hansen@linux.intel.com From: Dave Hansen Date: Thu, 26 Mar 2015 11:33:48 -0700 References: <20150326183327.64807530@viggo.jf.intel.com> In-Reply-To: <20150326183327.64807530@viggo.jf.intel.com> Message-Id: <20150326183348.DE9DE19B@viggo.jf.intel.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Dave Hansen The comment and code here are confusing. We do not currently allocate the bounds directory in the kernel. Signed-off-by: Dave Hansen --- b/arch/x86/mm/mpx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff -puN arch/x86/mm/mpx.c~x86-mpx-we-do-not-allocate-the-bounds-directory arch/x86/mm/mpx.c --- a/arch/x86/mm/mpx.c~x86-mpx-we-do-not-allocate-the-bounds-directory 2015-03-26 11:27:32.434453481 -0700 +++ b/arch/x86/mm/mpx.c 2015-03-26 11:27:32.437453616 -0700 @@ -51,8 +51,8 @@ static unsigned long mpx_mmap(unsigned l vm_flags_t vm_flags; struct vm_area_struct *vma; - /* Only bounds table and bounds directory can be allocated here */ - if (len != MPX_BD_SIZE_BYTES && len != MPX_BT_SIZE_BYTES) + /* Only bounds table can be allocated here */ + if (len != MPX_BT_SIZE_BYTES) return -EINVAL; down_write(&mm->mmap_sem); _