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, 26 Jul 2010 09:28:25 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Denys Vlasenko <vda.linux@...glemail.com>
Cc:	Tim Abbott <tabbott@...lice.com>, Tim Bird <tim.bird@...sony.com>,
	James Bottomley <James.Bottomley@...senpartnership.com>,
	linux-kernel@...r.kernel.org,
	Matt Fleming <matt@...sole-pimps.org>,
	linux-arch@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
	Michal Marek <mmarek@...e.cz>,
	Parisc List <linux-parisc@...r.kernel.org>
Subject: Re: Testing of function/data-sections on linux-2.6.35-rc4

On Mon, Jul 26, 2010 at 03:31:34AM +0200, Denys Vlasenko wrote:
> Hi Sam,
> 
> On Friday 23 July 2010 22:35, Sam Ravnborg wrote:
> > > 
> > > Then, in order to also garbage-collect the sections, I added
> > > 
> > > LDFLAGS_vmlinux += --gc-sections
> > > 
> > > in top-level Makefile.
> > > 
> > > This requires the additional patch (linux-2.6.35-rc4-fsgs.patch)
> > > which adds KEEP(section) directives to kernel linker stripts.
> > > Otherwise, linker will discard some crucial sections.
> > > 
> > 
> > Changelog does not address why you need:
> > 
> >      -Map $@...map
> > 
> > and what effect they have.
> 
> I didn't plan to push the last step (--gc-sections) to mainline yet.
> Thus the patch has debugging stuff in it.
> 
> 
> > And it is obvious that some archs should consolidate a little more from
> > asm-generic/vmlinux.lds.h.
> > But that said this patch looks much better than the initial versions posted.
> > 
> > How do you determine which sections needs the KEEP()?
> > Worth documenting for future when we add new sections.
> 
> No problem, I will be adding comments at every KEEP() why it's needed.

A general comment in vmlinux.lds.h and a careful explanation
in the changelog should be enough.

You should not comment each of the KEEP().

	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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ