linux-kernel - Re: v2.6.28-rc2: x86_32 relocation regression?

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1227576620.2442.7.camel@yhuang-dev.sh.intel.com>
Date:	Tue, 25 Nov 2008 09:30:20 +0800
From:	Huang Ying <ying.huang@...el.com>
To:	Vegard Nossum <vegard.nossum@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: v2.6.28-rc2: x86_32 relocation regression?

Hi, Vegard,

On Tue, 2008-11-25 at 05:19 +0800, Vegard Nossum wrote:
[...]
> It looks like everything was offset by 0xe00000:
> 
>     $ addr2line -e vmlinux c119e613
>     arch/x86/lib/string_32.c:20

Because relocation is supported in recent Linux kernel, it is possible
that the run-time address is different with compile-time address. In
most cases, the kernel will be loaded into 0x100000 during boot, so the
kernel run-time address range from 0xc0100000 on. But it seems that your
kernel compile-time address range from 0xc0f00000 on. Please check
CONFIG_PHYSICAL_START in your .config. In most cases, it will be set to
0x100000, so that it is same as run-time address in most cases.

Best Regards,
Huang Ying

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)