[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20111009134725.GD4586@localhost.pp.htv.fi>
Date: Sun, 9 Oct 2011 16:47:26 +0300
From: Adrian Bunk <bunk@...sta.de>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Andrew Lutomirski <luto@....edu>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm00@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Arjan van de Ven <arjan@...radead.org>
Subject: [3.1 patch] x86 vsyscall_64.c: 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 <bunk@...sta.de>
---
arch/x86/kernel/vsyscall_64.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/vsyscall_64.c b/arch/x86/kernel/vsyscall_64.c
index 18ae83d..4ab7e32 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;
}
Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)
Powered by blists - more mailing lists