From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932337AbbEHS7u (ORCPT ); Fri, 8 May 2015 14:59:50 -0400 Received: from mga09.intel.com ([134.134.136.24]:23081 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753623AbbEHS7h (ORCPT ); Fri, 8 May 2015 14:59:37 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,391,1427785200"; d="scan'208";a="707424913" Subject: [PATCH 06/19] 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: Fri, 08 May 2015 11:59:51 -0700 References: <20150508185948.4C19F4B0@viggo.jf.intel.com> In-Reply-To: <20150508185948.4C19F4B0@viggo.jf.intel.com> Message-Id: <20150508185951.971F11F2@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-05-08 11:46:12.671657450 -0700 +++ b/arch/x86/mm/mpx.c 2015-05-08 11:46:12.675657630 -0700 @@ -47,8 +47,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); _