Re: [patch] i386, vdso=[0|1] boot option and /proc/sys/vm/vdso_enabled

From: Zachary Amsden
Date: Sat May 20 2006 - 06:11:35 EST

Andrew Morton wrote:
Zachary Amsden <zach@xxxxxxxxxx> wrote:
Please try my patch - sent earlier, but attached again. It will tell you with 100% confidence if the problem is with userspace expecting the vsyscall page to be at a particular address.

[bogo-fixmap text/plain (645 bytes)]

Index: linux-2.6.17-rc/include/asm-i386/fixmap.h
--- linux-2.6.17-rc.orig/include/asm-i386/fixmap.h 2006-03-19 21:53:29.000000000 -0800
+++ linux-2.6.17-rc/include/asm-i386/fixmap.h 2006-05-19 18:16:00.000000000 -0700
@@ -20,7 +20,7 @@
* Leave one empty page between vmalloc'ed areas and
* the start of the fixmap.
-#define __FIXADDR_TOP 0xfffff000
+#define __FIXADDR_TOP 0xffbff000

The machine runs OK with that applied and with
move-vsyscall-page-out-of-fixmap-into-normal-vma-as-per-mmap.patch not

Err. That implies that there is likely a problem in the kernel patch, not in userspace, Let's look more closely at move-vsyscall-page-out-of-fixmap-into-normal-vma-as-per-mmap and see if there is something missing.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at