linux-kernel - Re: [RFC PATCH] linker script: unify usage of discard definition

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:	Sun, 5 Jul 2009 00:37:17 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Mike Frysinger <vapier.adi@...il.com>
Cc:	Tejun Heo <tj@...nel.org>,
	"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Michal Simek <monstr@...str.eu>,
	microblaze-uclinux@...e.uq.edu.au, Sam Ravnborg <sam@...nborg.org>,
	Tony Luck <tony.luck@...el.com>
Subject: Re: [RFC PATCH] linker script: unify usage of discard definition

On Sat, Jul 04, 2009 at 01:51:04AM -0400, Mike Frysinger wrote:
> On Fri, Jul 3, 2009 at 19:37, Tejun Heo wrote:
> > +/*
> > + * DISCARDS must be the last and archs which want some of the default
> > + * discarded sections in the kernel image can do so by putting them in
> > + * earlier section definition.
> > + */
> 
> i would add to the comment that some people want to discard exit
> text/data at runtime rather than link time due to cross-section
> references such as alt instructions, bug table, eh_frame, etc...
> 
> otherwise, looks good to me.  thanks !
> 
> Acked-by: Mike Frysinger <vapier@...too.org>

Agreed, as this was a source of confusion initially it is certainly worth
documenting the next time someone is scratching their head thinking about
the variations ;-)

Acked-by: Paul Mundt <lethal@...ux-sh.org>
--
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/