From: Dave Hansen <dave@sr71.net>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, tglx@linutronix.de, Dave Hansen <dave@sr71.net>,
dave.hansen@linux.intel.com
Subject: [PATCH 10/16] x86, mpx: we do not allocate the bounds directory
Date: Tue, 31 Mar 2015 17:46:36 -0700 [thread overview]
Message-ID: <20150401004636.D65B5530@viggo.jf.intel.com> (raw)
In-Reply-To: <20150401004623.894DF37A@viggo.jf.intel.com>
From: Dave Hansen <dave.hansen@linux.intel.com>
The comment and code here are confusing. We do not currently
allocate the bounds directory in the kernel.
Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
---
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-31 16:41:59.236415060 -0700
+++ b/arch/x86/mm/mpx.c 2015-03-31 16:41:59.239415195 -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);
_
next prev parent reply other threads:[~2015-04-01 0:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 0:46 [PATCH 00/16] x86, mpx updates for 4.1 (take 4) Dave Hansen
2015-04-01 0:46 ` [PATCH 01/16] x86, fpu: wrap get_xsave_addr() to make it safer Dave Hansen
2015-04-22 10:40 ` Borislav Petkov
2015-04-22 13:16 ` Oleg Nesterov
2015-04-22 13:31 ` Borislav Petkov
2015-04-22 14:56 ` Dave Hansen
2015-04-22 15:17 ` Thomas Gleixner
2015-04-22 15:21 ` Borislav Petkov
2015-04-22 15:26 ` Thomas Gleixner
2015-04-22 16:02 ` Dave Hansen
2015-04-22 15:32 ` Oleg Nesterov
2015-04-22 15:58 ` Borislav Petkov
2015-04-01 0:46 ` [PATCH 02/16] x86, mpx: use new tsk_get_xsave_addr() Dave Hansen
2015-04-01 0:46 ` [PATCH 03/16] x86, mpx: trace #BR exceptions Dave Hansen
2015-04-01 0:46 ` [PATCH 04/16] x86, mpx: trace entry to bounds exception paths Dave Hansen
2015-04-01 0:46 ` [PATCH 05/16] x86, mpx: trace ranged MPX operations Dave Hansen
2015-04-01 0:46 ` [PATCH 06/16] x86, mpx: trace allocation of new bounds tables Dave Hansen
2015-04-01 0:46 ` [PATCH 07/16] x86, mpx: boot-time disable Dave Hansen
2015-04-01 0:46 ` [PATCH 08/16] x86: make is_64bit_mm() widely available Dave Hansen
2015-04-01 0:46 ` [PATCH 09/16] x86: make __VIRTUAL_MASK safe to use on 32 bit Dave Hansen
2015-04-01 0:46 ` Dave Hansen [this message]
2015-04-01 0:46 ` [PATCH 11/16] x86, mpx: remove redundant MPX_BNDCFG_ADDR_MASK Dave Hansen
2015-04-01 0:46 ` [PATCH 12/16] x86, mpx: Add temporary variable to reduce masking Dave Hansen
2015-04-01 0:46 ` [PATCH 13/16] x86, mpx: new directory entry to addr helper Dave Hansen
2015-04-01 0:46 ` [PATCH 14/16] x86, mpx: do 32-bit-only cmpxchg for 32-bit apps Dave Hansen
2015-04-01 0:46 ` [PATCH 15/16] x86, mpx: support 32-bit binaries on 64-bit kernel Dave Hansen
2015-04-01 0:46 ` [PATCH 16/16] x86, mpx: allow mixed binaries again Dave Hansen
2015-04-21 15:39 ` [PATCH 00/16] x86, mpx updates for 4.1 (take 4) Dave Hansen
2015-04-22 10:49 ` Borislav Petkov
2015-04-22 14:43 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150401004636.D65B5530@viggo.jf.intel.com \
--to=dave@sr71.net \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).