Benjamin Herrenschmidt b...@kernel.crashing.org writes:
Maybe a better fix is to force alignment in the kernel by requesting
size + 64k - 4k and aligning it.
Sure you are right.
Andreas.
From b9441a3d2148d439e2730def3222a7b70dccc432 Mon Sep 17 00:00:00 2001
From: Andreas Schwab
Andreas Schwab sch...@linux-m68k.org writes:
Anton Blanchard an...@samba.org writes:
On 64bit applications the VDSO is the only thing in segment 0. Since the VDSO
is position independent we can remove the hint and let get_unmapped_area pick
an area.
This breaks gdb. The section table in
Andreas Schwab sch...@linux-m68k.org writes:
Andreas Schwab sch...@linux-m68k.org writes:
Anton Blanchard an...@samba.org writes:
On 64bit applications the VDSO is the only thing in segment 0. Since the
VDSO
is position independent we can remove the hint and let get_unmapped_area
pick
On Sat, 2009-10-03 at 16:51 +0200, Andreas Schwab wrote:
Andreas Schwab sch...@linux-m68k.org writes:
Andreas Schwab sch...@linux-m68k.org writes:
Anton Blanchard an...@samba.org writes:
On 64bit applications the VDSO is the only thing in segment 0. Since the
VDSO
is position
Anton Blanchard an...@samba.org writes:
On 64bit applications the VDSO is the only thing in segment 0. Since the VDSO
is position independent we can remove the hint and let get_unmapped_area pick
an area.
This breaks gdb. The section table in the VDSO image when mapped into
the process no
On Tue, 2009-07-14 at 16:53 +1000, Anton Blanchard wrote:
plain text document attachment (move_vdso_v2)
On 64bit applications the VDSO is the only thing in segment 0. Since the VDSO
is position independent we can remove the hint and let get_unmapped_area pick
an area. This will mean the vdso
Hi Ben,
Don't we lose randomization ? Or do we randomize the whole mem map
nowadays ?
The start of the top down mmap region is randomized, so the VDSO will be in a
different position each time. A quick example:
run 1:
fffb01f6000-fffb01f9000 r-xp 00:00 0 [vdso]
