linux-kernel - [RFC][PATCH 0/7] x86, mpx: Support larger address space (MAWA) (v2)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20170201232408.FA486473@viggo.jf.intel.com>
Date:   Wed, 01 Feb 2017 15:24:08 -0800
From:   Dave Hansen <dave.hansen@...ux.intel.com>
To:     linux-kernel@...r.kernel.org
Cc:     linux-mm@...ck.org, x86@...nel.org,
        kirill.shutemov@...ux.intel.com,
        Dave Hansen <dave.hansen@...ux.intel.com>
Subject: [RFC][PATCH 0/7] x86, mpx: Support larger address space (MAWA) (v2)

Changes from v1:
 * Added selftests support for this feature
 * Removed "mawa" nomenclature from all variables and functions
 * Added patch to cram new "mawa" value into existing MPX space
   in mmu_context_t
 * Optimize the switch_mpx_bd() code with a likely().  We will
   need to do a bit more analysis here to see what the cheapest
   way to do this is.

--

Kirill is chugging right along getting his 5-level paging[1] patch set
ready to be merged.  I figured I'd share an early draft of the MPX
support that will to go along with it.

Background: there is a lot more detail about what bounds tables are in
the changelog for fe3d197f843.  But, basically MPX bounds tables help
us to store the ranges to which a pointer is allowed to point.  The
tables are walked by hardware and they are indexed by the virtual
address of the pointer being checked.

A larger virtual address space (from 5-level paging) means that we
need larger tables.  5-level paging hardware includes a feature called
MPX Address-Width Adjust (MAWA) that grows the bounds tables so they
can address the new address space.  MAWA is controlled independently
from the paging mode (via an MSR) so that old MPX binaries can run on
new hardware and kernels supporting 5-level paging.

But, since userspace is responsible for allocating the table that is
growing (the directory), we need to ensure that userspace and the
kernel agree about the size of these tables and the kernel can set the
MSR appropriately.

These are not quite ready to get applied anywhere, but I don't expect
the basics to change unless folks have big problems with this.  The
only big remaining piece of work is to update the MPX selftest code.

Dave Hansen (7):
      x86, mpx: introduce per-mm MPX table size tracking
      x86, mpx: update MPX to grok larger bounds tables
      x86, mpx: extend MPX prctl() to pass in size of bounds directory
      x86, mpx: context-switch new MPX address size MSR
      x86, mpx: shrink per-mm MPX data
      x86, mpx, selftests: Use prctl header instead of magic numbers
      x86, mpx: update MPX selftest to test larger bounds dir

 arch/x86/include/asm/mmu.h                  |   9 +-
 arch/x86/include/asm/mpx.h                  |  77 ++++++++--
 arch/x86/include/asm/msr-index.h            |   1 +
 arch/x86/include/asm/processor.h            |   6 +-
 arch/x86/mm/mpx.c                           | 100 +++++++++++--
 arch/x86/mm/tlb.c                           |  46 ++++++
 kernel/sys.c                                |   6 +-
 tools/testing/selftests/x86/mpx-hw.h        |  23 ++-
 tools/testing/selftests/x86/mpx-mini-test.c | 156 +++++++++++++++-----
 9 files changed, 349 insertions(+), 75 deletions(-)

1. https://software.intel.com/sites/default/files/managed/2b/80/5-level_paging_white_paper.pdf