linux-kernel - Re: [PATCH 1/5] vmlinux.lds.h: Include *(.text.*) in TEXT

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:	Mon, 14 Jun 2010 20:33:53 +0100
From:	Matt Fleming <matt@...sole-pimps.org>
To:	Tim Abbott <tabbott@...lice.com>
Cc:	linux-arch@...r.kernel.org, Arnd Bergmann <arnd@...db.de>,
	linux-kernel@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>,
	Michal Marek <mmarek@...e.cz>,
	Denys Vlasenko <vda.linux@...glemail.com>,
	James Bottomley <James.Bottomley@...senPartnership.com>
Subject: Re: [PATCH 1/5] vmlinux.lds.h: Include *(.text.*) in TEXT_TEXT

On Mon, 14 Jun 2010 10:32:46 -0400 (EDT), Tim Abbott <tabbott@...lice.com> wrote:
> 
> I was planning to submit in the next couple weeks a change that adds 
> support for building the kernel with -ffunction-sections -fdata-sections, 
> which would have as a piece of it adding to TEXT_TEXT the following 
> expression:
> 
> 	*(.text.[A-Za-z$_]*)	/* handle -ffunction-sections */\
> 
> which should match the .text.foo sections generated by -ffunction-sections 
> but not the kernel's special sections which now all have names of the form 
> .text..foo.  I suspect after that change, the cleanup of deleting .text.* 
> from the various architecture linker scripts that reference it should be 
> possible.

Do these special kernel sections include things like the parisc
.text.do_softirq, .text.sys_exit, etc? James raised a good objection to
the parisc patch of this series. I'm guessing most people saw it already
but I'll paste it here for reference,


    This would destroy all of the named parisc text ordering we do above the
    removed line because now you'd have swept up all the function sections
    before we get to them, won't it?

    The ordering is an execution speed up on 32 bit systems because our
    relative jump is so short.

    James

Will you changes handle this OK?
--
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/