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-next>] [day] [month] [year] [list]
Date:	Mon, 09 Mar 2009 21:37:50 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	the arch/x86 maintainers <x86@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Absolute symbols in vmlinux_64.lds.S



Yinghai Lu <yinghai@...nel.org> wrote:

>Jeremy Fitzhardinge wrote:
>> Why does vmlinux_64.lds.S use absolute symbols for things like
>> __bss_start/stop:
>> 
>>  __bss_start = .;        /* BSS */
>>  .bss : AT(ADDR(.bss) - LOAD_OFFSET) {
>>     *(.bss.page_aligned)
>>     *(.bss)
>>     }
>>  __bss_stop = .;
>> 
>> 
>> vmlinux_32.lds.S puts __bss_start/stop into the .bss section itself.  Is
>> there some particular reason they need to be absolute symbols
>> (relocation?).
>> 
>
>they are the same.

Do you mean it makes no difference?

	J
-- 
Sent from my Android phone with K-9. Please excuse my brevity.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ