linux-kernel - Re: [PATCH 7/11] i386: Kallsyms generate relocatable symbols

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]

Date:	Mon, 06 Nov 2006 08:34:57 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Haavard Skinnemoen <hskinnemoen@...el.com>
CC:	vgoyal@...ibm.com,
	linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Reloc Kernel List <fastboot@...ts.osdl.org>,
	ebiederm@...ssion.com, akpm@...l.org, ak@...e.de,
	magnus.damm@...il.com, lwang@...hat.com, dzickus@...hat.com,
	maneesh@...ibm.com
Subject: Re: [PATCH 7/11] i386: Kallsyms generate relocatable symbols

Haavard Skinnemoen wrote:
> On Mon, 23 Oct 2006 15:37:48 -0400
> Vivek Goyal <vgoyal@...ibm.com> wrote:
> 
>> Add the _text symbol definitions to the architectures which don't
>> define it otherwise linker will fail.
> 
> I get lots of this when building latest -mm for avr32:
> 
> .tmp_kallsyms2.S:643: Warning: right operand is a bignum; integer 0
> assumed
> 
> Reverting this patch makes the warnings go away. I think it's
> because on avr32, .init is the first section, not .text, so many of the
> offsets become negative and kallsyms doesn't seem to handle this very
> well. Here's a few lines from .tmp_kallsyms2.S:
> 
> kallsyms_addresses:
>         PTR     _text + 0xffffffffffff4000
>         PTR     _text + 0xffffffffffff4000
> 
> Any idea how to fix this? Could we introduce a new symbol that always
> marks the start of the image perhaps?
> 

Maybe we should generate it as a signed value (-0x8000) instead of an 
unsigned value.

	-hpa
-
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/