Commit:     cf8dc57cbac0fe089308f57c333ab763c36782ff
Parent:     75723957673bfa10c98b735259f891cc79cf0450
Author:     Andi Kleen <[EMAIL PROTECTED]>
AuthorDate: Mon Oct 1 01:20:08 2007 -0700
Committer:  Linus Torvalds <[EMAIL PROTECTED]>
CommitDate: Mon Oct 1 19:21:30 2007 -0700

    x86_64: increase VDSO_TEXT_OFFSET for ancient binutils
    For some reason old binutils genertate larger headers so increase the text
    offset of the vdso to avoid linker errors.
    Roland McGrath explains:
      "There are extra symbols in the '.dynsym' section that are responsible
       for the size difference (They also cause corresponding inflation in
       Older ld's wrongly generated these unneeded symbols in .dynsym.  This
       was fixed not all that long ago (2006); binutils- might be
       the first fixed version, but I have not verified for sure where the
       cutoff was.
       The unneeded symbols et al from old ld add almost 700 bytes excess.
       This limits fairly tightly the amount by which the actual text and
       data in the vDSO can grow in the future without pushing the whole
       file over 4kb.  If it does grow later on, we should consider changing
       the layout with a config option or something to pack it better
       without that padding, when building the kernel with newer binutils."
    Signed-off-by: Andi Kleen <[EMAIL PROTECTED]>
    Cc: Roland McGrath <[EMAIL PROTECTED]>
    Cc: Badari Pulavarty <[EMAIL PROTECTED]>
    Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
    Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
 arch/x86_64/vdso/voffset.h |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86_64/vdso/voffset.h b/arch/x86_64/vdso/voffset.h
index 5304204..4af67c7 100644
--- a/arch/x86_64/vdso/voffset.h
+++ b/arch/x86_64/vdso/voffset.h
@@ -1 +1 @@
-#define VDSO_TEXT_OFFSET 0x500
+#define VDSO_TEXT_OFFSET 0x600
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to