Documentation/admin: Remove the vsyscall=native documentation
authorAndy Lutomirski <luto@kernel.org>
Thu, 27 Jun 2019 04:45:02 +0000 (21:45 -0700)
committerThomas Gleixner <tglx@linutronix.de>
Thu, 27 Jun 2019 22:04:38 +0000 (00:04 +0200)
The vsyscall=native feature is gone -- remove the docs.

Fixes: 076ca272a14c ("x86/vsyscall/64: Drop "native" vsyscalls")
Signed-off-by: Andy Lutomirski <luto@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Acked-by: Kees Cook <keescook@chromium.org>
Cc: Florian Weimer <fweimer@redhat.com>
Cc: Jann Horn <jannh@google.com>
Cc: stable@vger.kernel.org
Cc: Borislav Petkov <bp@alien8.de>
Cc: Kernel Hardening <kernel-hardening@lists.openwall.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Link: https://lkml.kernel.org/r/d77c7105eb4c57c1a95a95b6a5b8ba194a18e764.1561610354.git.luto@kernel.org
Documentation/admin-guide/kernel-parameters.txt

index 138f6664b2e29fe4ca71225fde00ac2ea695a941..0082d1e56999ec6d2ef0aec85476799397cedf0e 100644 (file)
                        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.