linux-kernel - Re: [PATCH] modpost: Ignore ARC specific non-alloc sections

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: <50E3C2B6.9010208@synopsys.com>
Date:	Wed, 2 Jan 2013 10:46:38 +0530
From:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:	Rusty Russell <rusty@...tcorp.com.au>
CC:	Sam Ravnborg <sam@...nborg.org>, Michal Marek <mmarek@...e.cz>,
	"Tony Lindgren" <tony@...mide.com>, <linux-kernel@...r.kernel.org>,
	<linux-arch@...r.kernel.org>
Subject: Re: [PATCH] modpost: Ignore ARC specific non-alloc sections

On Wednesday 02 January 2013 06:19 AM, Rusty Russell wrote:
> Sam Ravnborg <sam@...nborg.org> writes:
>
>> On Thu, Dec 27, 2012 at 04:17:20PM +0530, Vineet Gupta wrote:
>>> ARC relocatable object files contain one/more .gnu.linkonce.arcextmap.*
>>> sections (collated by kernel/vmlinux.lds into .arcextmap in final link).
>>> This section is used by debuggers to display the extension instructions
>>> and need-not be loaded by target (hence !SHF_ALLOC)
>>>
>>> The final kernel binary only needs .arcextmap entry in modpost's ignore
>>> list (section_white_list[]). However when building modules, modpost scans
>>> each object file individually, hence tripping on non-aggregated
>>> .gnu.linkonce.arcextmap.* entries as well.
>> The list exist for this particular purpose.
>> So acked.
> Applied, thanks!
>
> Cheers,
> Rusty.

Thanks Rusty.
I'll drop this patch from my series.

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