linux-kernel - Re: [PATCH] scripts: Make sortextable handle relocations.

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: <4F91EEA2.8020502@zytor.com>
Date:	Fri, 20 Apr 2012 16:17:54 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	David Daney <ddaney.cavm@...il.com>
CC:	Ralf Baechle <ralf@...ux-mips.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Michal Marek <mmarek@...e.cz>, linux-kernel@...r.kernel.org,
	linux-mips@...ux-mips.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] scripts: Make sortextable handle relocations.

On 04/20/2012 04:14 PM, David Daney wrote:
>>
>> I think Linus is right and the right thing to do is to switch to using
>> relative entries in the exception table; I am currently testing a
>> patchset to do exactly that (on x86).  It also has the benefit of making
>> the table half the size on x86-64.  Then we can just zero out the
>> .rel[a]__ex_table section and be done with it.
> 
> That's fine.
> 
> In any event we want to do build time sorting, this patch improves the
> original sortextable, so may be worthwhile as purely a cleanup.  I
> wanted to fix the relocation breakage, even if the eventual solution
> needs to be somewhat different.
> 

Yes... let me finish the patchset and then you can look at what is needed.

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