From ef4f84e9187dcd017ea0ab3976af4d3ba806ed95 Mon Sep 17 00:00:00 2001 From: Adrian Bunk Date: Sun, 9 Oct 2011 16:47:26 +0300 Subject: [PATCH] x86, vsyscall: Use better error message on bad pointers At least some UML versions run into this and need vsyscall=native for now. Signed-off-by: Adrian Bunk Cc: Andrew Lutomirski Cc: H. Peter Anvin Cc: Linus Torvalds Cc: Arjan van de Ven Link: http://lkml.kernel.org/r/20111009134725.GD4586@localhost.pp.htv.fi Signed-off-by: Ingo Molnar --- arch/x86/kernel/vsyscall_64.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/kernel/vsyscall_64.c b/arch/x86/kernel/vsyscall_64.c index 18ae83dd1cd7..4ab7e322e0e6 100644 --- a/arch/x86/kernel/vsyscall_64.c +++ b/arch/x86/kernel/vsyscall_64.c @@ -206,7 +206,7 @@ bool emulate_vsyscall(struct pt_regs *regs, unsigned long address) * vsyscalls harder, generate SIGSEGV here as well. */ warn_bad_vsyscall(KERN_INFO, regs, - "vsyscall fault (exploit attempt?)"); + "vsyscall fault (exploit attempt?) - if this is a legitimate program boot with vsyscall=native (read kernel-parameters.txt for the security implications)"); goto sigsegv; } -- 2.39.5