linux-kernel - Re: vdso.so mislinked by buggy linker was Re: Linus 2.6.23-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <200707231644.25539.ak@suse.de>
Date:	Mon, 23 Jul 2007 16:44:25 +0200
From:	Andi Kleen <ak@...e.de>
To:	Jakub Jelinek <jakub@...hat.com>
Cc:	Andre Noll <maan@...temlinux.org>, linux-kernel@...r.kernel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: vdso.so mislinked by buggy linker was Re: Linus 2.6.23-rc1


> Looking at vdso.lds.S, if you change just VDSO_TEXT_OFFSET to 0xc00 and
> don't tweak the linker script, then you jump backwards with the dot, you
> should even get a linker warning about it:
> 
>   . = VDSO_PRELINK + VDSO_TEXT_OFFSET;
> 
>   .text           : { *(.text) }                :text
>   .text.ptr       : { *(.text.ptr) }            :text
>   . = VDSO_PRELINK + 0x900;
> 
> Guess that 0x900 should have been VDSO_TEXT_OFFSET + 0x400 or something
> similar.  Also note that it is highly desirable to fit the whole vdso into
> one page, so increasing VDSO_TEXT_OFFSET etc. offsets too much is just
> wasting memory.  From the above dump, VDSO_TEXT_OFFSET 0x500 is too low,
> but 0x600 should work, 

The reporter reported only 0xc00 worked, which is mysterious.

Also how do we get rid of the 1MB padding on those binutils? 

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/