Thread (24 messages) 24 messages, 8 authors, 2018-01-18

Re: [PATCH v2 00/19] prevent bounds-check bypass via speculative execution

From: Tony Luck <hidden>
Date: 2018-01-13 00:15:20
Also in: linux-arch, linux-media, linux-scsi, linux-wireless, lkml

On Thu, Jan 11, 2018 at 5:19 PM, Linus Torvalds
[off-list ref] wrote:
Should the array access in entry_SYSCALL_64_fastpath be made to use
the masking approach?
That one has a bounds check for an inline constant.

     cmpq    $__NR_syscall_max, %rax

so should be safe.

The classic Spectre variant #1 code sequence is:

int array_size;

       if (x < array_size) {
               something with array[x]
       }

which runs into problems because the array_size variable may not
be in cache, and while the CPU core is waiting for the value it
speculates inside the "if" body.

The syscall entry is more like:

#define ARRAY_SIZE 10

     if (x < ARRAY_SIZE) {
          something with array[x]
     }

Here there isn't any reason for speculation. The core has the
value of 'x' in a register and the upper bound encoded into the
"cmp" instruction.  Both are right there, no waiting, no speculation.

-Tony
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help