linux-kernel - Re: 2.6.23-rc8-mm1 -- powerpc link failure

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: <20070927120308.GJ2213@shadowen.org>
Date:	Thu, 27 Sep 2007 13:03:08 +0100
From:	Andy Whitcroft <apw@...dowen.org>
To:	Jiri Kosina <jkosina@...e.cz>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Franck Bui-Huu <vagabon.xyz@...il.com>,
	linux-kernel@...r.kernel.org,
	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
Subject: Re: 2.6.23-rc8-mm1 -- powerpc link failure

> actually, my first patch wasn't using weak symbols, but I have been 
> convinced that it's the way to go(tm). Please see 
> http://lkml.org/lkml/2007/9/1/131 and the ongoing thread.
> 
> I am fine with replacing the brk randomization patch with the one that 
> wasn't using weak symbols (posted in the mentioned thread too), I have no 
> strong opinion either way.

Ok, this problem seems to still persist in 2.6.23-rc8-mm2.  It seems
we have three options from here:

1) update the compiler support list to exclude these compilers, or
2) back this change out, or
3) switch to the version not using __weak.

The latter seems to be the least intrusive change.  As no-one closer
to the problem is stepping up to make the decision I will propose
we go with the third option here.

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