| commit | 22c5ace7290b792faf64ffe90cf933950fbf52db | |
| author | Jan Beulich <jbeulich@novell.com> | |
| Tue, 13 Feb 2007 12:26:26 +0000 (13 13:26 +0100) | ||
| committer | Andi Kleen <andi@basil.nowhere.org> | |
| Tue, 13 Feb 2007 12:26:26 +0000 (13 13:26 +0100) | ||
| tree | 28f97a1f6bf22ed91424a8e7810e285bf18c9a79 | treesnapshot (tar.gz zip) |
| parent | 98838ec984b78c625bbf9a5daaf001cd216b8f86 | commitdiff |
[PATCH] i386: Fix broken CONFIG_COMPAT_VDSO on i386
After updating several machines to 2.6.20, I can't boot anymore the single
one of them that supports the NX bit and is configured as a 32-bit system.
My understanding is that the VDSO changes in 2.6.20-rc7 were not fully
cooked, in that with that config option enabled VDSO_SYM(x) now equals
x, meaning that an address in the fixmap area is now being passed to
apps via AT_SYSINFO. However, the page is mapped with PAGE_READONLY
rather than PAGE_READONLY_EXEC.
I'm not certain whether having app code go through the fixmap area is
intended, but in case it is here is the simple patch that makes things work
again.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andi Kleen <ak@suse.de>
After updating several machines to 2.6.20, I can't boot anymore the single
one of them that supports the NX bit and is configured as a 32-bit system.
My understanding is that the VDSO changes in 2.6.20-rc7 were not fully
cooked, in that with that config option enabled VDSO_SYM(x) now equals
x, meaning that an address in the fixmap area is now being passed to
apps via AT_SYSINFO. However, the page is mapped with PAGE_READONLY
rather than PAGE_READONLY_EXEC.
I'm not certain whether having app code go through the fixmap area is
intended, but in case it is here is the simple patch that makes things work
again.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andi Kleen <ak@suse.de>
| arch/i386/kernel/sysenter.c | diffblobblamehistory |