@@ -45,7 +45,7 @@ is how we expect the compiler, application and kernel to work together.
4545 MPX-instrumented.
46463) The kernel detects that the CPU has MPX, allows the new prctl() to
4747 succeed, and notes the location of the bounds directory. Userspace is
48- expected to keep the bounds directory at that locationWe note it
48+ expected to keep the bounds directory at that location. We note it
4949 instead of reading it each time because the 'xsave' operation needed
5050 to access the bounds directory register is an expensive operation.
51514) If the application needs to spill bounds out of the 4 registers, it
@@ -167,7 +167,7 @@ If a #BR is generated due to a bounds violation caused by MPX.
167167We need to decode MPX instructions to get violation address and
168168set this address into extended struct siginfo.
169169
170- The _sigfault feild of struct siginfo is extended as follow:
170+ The _sigfault field of struct siginfo is extended as follow:
171171
17217287 /* SIGILL, SIGFPE, SIGSEGV, SIGBUS */
17317388 struct {
@@ -240,5 +240,5 @@ them at the same bounds table.
240240This is allowed architecturally. See more information "Intel(R) Architecture
241241Instruction Set Extensions Programming Reference" (9.3.4).
242242
243- However, if users did this, the kernel might be fooled in to unmaping an
243+ However, if users did this, the kernel might be fooled in to unmapping an
244244in-use bounds table since it does not recognize sharing.
0 commit comments