linux-kernel - Re: [PATCH 0/6] section name cleanup for mn10300

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]

Date:	Fri, 1 May 2009 16:48:58 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	David Howells <dhowells@...hat.com>
Cc:	Tim Abbott <tabbott@....EDU>,
	Linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Anders Kaseorg <andersk@....EDU>,
	Waseem Daher <wdaher@....EDU>,
	Denys Vlasenko <vda.linux@...glemail.com>,
	Jeff Arnold <jbarnold@....EDU>
Subject: Re: [PATCH 0/6] section name cleanup for mn10300

On Fri, May 01, 2009 at 03:35:19PM +0100, David Howells wrote:
> Tim Abbott <tabbott@....EDU> wrote:
> 
> > This patch series cleans up the section names on the mn10300
> > architecture.  It requires the architecture-independent macro
> > definitions from this patch series:
> 
> Interesting...  Whilst it compiles and links with no problems, this cleanup
> has the following detrimental effects:
> 
> None of these patches applied
> 
> 	   text    data     bss     dec     hex filename
> 	1879329   82980  321772 2284081  22da31 vmlinux
> 
> All of these patches applied:
> 
> 	   text    data     bss     dec     hex filename
> 	1879329   87076  321772 2288177  22ea31 vmlinux
> 
> Somewhere it eats an extra page.

This is likely due to moving around the sections and
we have got them in less perfect order.

I also thing 5/6 is wrong as it moves
init_task befoe _edata.

Could you try to back out them one by one
to see which one causes the extra memory waste.

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