linux-kernel - Re: [PATCH] x86_64: Some vmlinux.lds.S cleanups

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]

Message-ID: <20061026151241.GC11284@in.ibm.com>
Date:	Thu, 26 Oct 2006 11:12:41 -0400
From:	Vivek Goyal <vgoyal@...ibm.com>
To:	Jan Beulich <jbeulich@...ell.com>
Cc:	Andi Kleen <ak@....de>,
	linux kernel mailing list <linux-kernel@...r.kernel.org>,
	Ian Campbell <Ian.Campbell@...source.com>
Subject: Re: [PATCH] x86_64: Some vmlinux.lds.S cleanups

On Thu, Oct 26, 2006 at 03:52:47PM +0200, Jan Beulich wrote:
> >>> Vivek Goyal <vgoyal@...ibm.com> 26.10.06 15:44 >>>
> >On Thu, Oct 26, 2006 at 08:08:21AM +0100, Jan Beulich wrote:
> >> I was about to ack it when I saw that you left .bss in init - that doesn't seem
> >> too good an idea... Jan
> >> 
> >
> >Should I create a separate program header say "bss" for .bss section? Last
> >time when I suggested it you said there is no need to create a separate
> >program header for bss.
> 
> No, I continue to think .bss naturally belongs at the end of the data segment.
> 

Only disadvantage of this is that .bss becomes part of the compressed data
and size of vmlinux.bin and bzImage increases.

OTOH, all the sections being mapped in segment "user" are also effectively
data only. isn't it? So .bss coming after that would make sense.

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