linux-kernel - Re: [PATCH 00/24] Rename kernel's magic sections for compatibility with -ffunction-sections -fdata-sections

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 28 Feb 2010 23:03:46 -0500 (EST)
From:	Tim Abbott <tabbott@...lice.com>
To:	Michal Marek <mmarek@...e.cz>
cc:	Denys Vlasenko <vda.linux@...glemail.com>,
	Sam Ravnborg <sam@...nborg.org>,
	Haavard Skinnemoen <hskinnemoen@...el.com>,
	David Howells <dhowells@...hat.com>,
	linux-kernel@...r.kernel.org, Bjorn Wesen <bjornw@...s.com>,
	Tim Bird <tim.bird@...sony.com>,
	Anders Kaseorg <andersk@...lice.com>,
	Waseem Daher <wdaher@...lice.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Andi Kleen <andi@...stfloor.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"H. Peter Anvin" <hpa@...or.com>,
	Barry Song <barry.song@...log.com>,
	Mike Frysinger <vapier@...too.org>
Subject: Re: [PATCH 00/24] Rename kernel's magic sections for compatibility
 with -ffunction-sections -fdata-sections

On Sat, 20 Feb 2010, Denys Vlasenko wrote:

> Here is a new version of the -ffunction-sections -fdata-sections patch
> series based on current Linus tree.

Aside from patch 17, which I would prefer that Haavard review, these 
patches look correct (and patch 17 can be safely dropped).  Please 
consider the rest of Denys' patches in this patch series

Acked-by: Tim Abbott <tabbott@...lice.com>

The patches still apply fine on Linus' current master.  There are no merge 
conflicts with linux-next's current master, but we will need to do 
something to merge with

"Blackfin: initial XIP support"

in linux-next, which introduces a direct reference to .data.percpu.* (not 
using the normal PERCPU macros so they can put .data.percpu content inside 
the .init.data section).  That conflict looks easy to deal with by adding 
a new macro to handle this case (CCing the author and blackfin maintainer; 
it's possible that this blackfin patch is going in soon, in which case we 
can just rebase these patches on top).

Michal, what are your thoughts on this patch series?  The kbuild tree 
would be a reasonable path for merging these patches.

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