RISC-V: Don't use a global include guard for uapi/asm/syscalls.

From: Palmer Dabbelt
Date: Thu Aug 09 2018 - 18:34:31 EST

Next message: kernel test robot: "a13c600e15 ("x86/mm/pti: Move user W+X check into .."): WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:283 note_page"
Previous message: Leonardo BrÃs: "[PATCH v3 2/3] staging: fbtft: Replaces (1 << n) for macro BIT(n) - Style"
Next in thread: Palmer Dabbelt: "[PATCH v3 2/2] RISC-V: Don't use a global include guard for uapi/asm/syscalls.h"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

It turns out that we weren't actually hooking sys_riscv_flush_icache
into the syscall table, which results in any flush_icache() call that
escapes the vDSO to silently do nothing.

Changes since v2:

* sys_riscv_flush_icache actually flushes the icache when SMP=n. Thanks
to Andrew for pointing out the I screwed it up!

Changes since v1:

* sys_riscv_flush_icache is now defined even when SMP=n, which allows
this patch set to build against SMP=n and SMP=y.

Next message: kernel test robot: "a13c600e15 ("x86/mm/pti: Move user W+X check into .."): WARNING: CPU: 0 PID: 1 at arch/x86/mm/dump_pagetables.c:283 note_page"
Previous message: Leonardo BrÃs: "[PATCH v3 2/3] staging: fbtft: Replaces (1 << n) for macro BIT(n) - Style"
Next in thread: Palmer Dabbelt: "[PATCH v3 2/2] RISC-V: Don't use a global include guard for uapi/asm/syscalls.h"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]