diff options
authorAndy Lutomirski <>2019-06-26 21:45:02 -0700
committerGreg Kroah-Hartman <>2019-07-14 08:11:18 +0200
commita2a24b57c27ab039122d447940be7d346f9bbdaf (patch)
parent8a815007f5fe292fa8ef082663e1259b9ae0571b (diff)
Documentation/admin: Remove the vsyscall=native documentation
commit d974ffcfb7447db5f29a4b662a3eaf99a4e1109e upstream. The vsyscall=native feature is gone -- remove the docs. Fixes: 076ca272a14c ("x86/vsyscall/64: Drop "native" vsyscalls") Signed-off-by: Andy Lutomirski <> Signed-off-by: Thomas Gleixner <> Acked-by: Kees Cook <> Cc: Florian Weimer <> Cc: Jann Horn <> Cc: Cc: Borislav Petkov <> Cc: Kernel Hardening <> Cc: Peter Zijlstra <> Link: Signed-off-by: Greg Kroah-Hartman <>
1 files changed, 0 insertions, 6 deletions
diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
index a29301d6e6c6..1cee1174cde6 100644
--- a/Documentation/admin-guide/kernel-parameters.txt
+++ b/Documentation/admin-guide/kernel-parameters.txt
@@ -4976,12 +4976,6 @@
emulate [default] Vsyscalls turn into traps and are
emulated reasonably safely.
- native Vsyscalls are native syscall instructions.
- This is a little bit faster than trapping
- and makes a few dynamic recompilers work
- better than they would in emulation mode.
- It also makes exploits much easier to write.
none Vsyscalls don't work at all. This makes
them quite hard to use for exploits but
might break your system.