linux-kernel - Re: Please include const-sections into linux-next

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:	Fri, 14 Oct 2011 17:26:44 -0500
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: Please include const-sections into linux-next

On Fri, 2011-10-14 at 01:38 +0200, Andi Kleen wrote:
> Stephen,
> 
> Please include 
> git://github.com/andikleen/linux-misc.git const-sections
> in linux-next. This has a tree sweep to fix all kind of constant 
> section issues.
> 
> I intend to send Linus a pull request next cycle and would like 
> to get some testing in next first.
> 
> I got various acks last time it was posted and added them all.
> In general it falls more in the "trivial" category, but it's 
> rather large and all over so I may have made a mistake.

It's not incredibly trivial: it causes a compile failure on parisc:

mm/percpu.c:1372: error: __setup_str_percpu_alloc_setup causes a section
type conflict
make[1]: *** [mm/percpu.o] Error 1

I have no idea why, though.

James


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