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]
Message-ID: <alpine.DEB.1.10.1006141014360.1432@dr-wily.mit.edu>
Date:	Mon, 14 Jun 2010 10:32:46 -0400 (EDT)
From:	Tim Abbott <tabbott@...lice.com>
To:	Matt Fleming <matt@...sole-pimps.org>
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>
Subject: Re: [PATCH 1/5] vmlinux.lds.h: Include *(.text.*) in TEXT_TEXT

On Mon, 14 Jun 2010, Matt Fleming wrote:

> Many architectures collect text sections beginning with '.text.' in
> their .text section, so move this pattern into TEXT_TEXT to stop them
> all having to duplicate the pattern in their arch/ linker scripts.

Hi Matt,

I think this change could result in problems such as the page-aligned text 
sections (recently renamed from .text.page_aligned to .text..page_aligned) 
that exist in some architectures being included the main text section in a 
non-page-aligned fashion (and similar issues for other .text.foo 
sections).

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.

	-Tim Abbott
--
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