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] [day] [month] [year] [list]
Message-ID: <20121123212559.GW15971@htj.dyndns.org>
Date:	Fri, 23 Nov 2012 13:25:59 -0800
From:	Tejun Heo <tj@...nel.org>
To:	Jan Engelhardt <jengelh@...i.de>
Cc:	cl@...ux-foundation.org, linux-mm@...ck.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: percpu section failure with Gold linker

Hello, Jan.

On Fri, Nov 23, 2012 at 09:44:02PM +0100, Jan Engelhardt wrote:
> when compiling a kernel with the gold linker (3.7.0-rc6 26d29d06ea0204, 
> gcc-4.7 and binutils-2.23 in my case), certain pcpu symbols are 
> seemingly errneously copied over from .o files to .ko files, leading to 
> a hard warning during depmod:
> 
> 	gold$ make -j8 LD=gold HOSTLD=gold
> 	gold$ make modules_install INSTALL_MOD_PATH=/tmp/foo
> 	[...]
> 	WARNING: /tmp/foo/lib/modules/3.7.0-rc6-jng6-default+
> 	/kernel/net/rds/rds_tcp.ko needs unknown symbol
> 	__pcpu_scope_rds_tcp_stats

Yeah, this is from the nasty tricks percpu plays to get percpu decls
working on s390 and alpha.  Take a look at
DECLARE/DEFINE_PER_CPU_SECTION() definitions in
include/linux/percpu-defs.h for details.

> This happens with many modules using percpu; looking at things with nm 
> reveals:
> 
> 	gold/net/ipv6$ nm ipv6.o | grep __pcpu_
> 	0000000000000000 D __pcpu_unique_ipv6_cookie_scratch
> 	gold/net/ipv6$ nm ipv6.ko | grep __pcpu_
> 	                 U __pcpu_unique_ipv6_cookie_scratch
> 
> On the other hand, in a linux tree built with the original ld (ld.bfd), 
> things look like:
> 
> 	bfd$ make -j8
> 	[...]
> 	bfd/net/ipv6$ nm ipv6.o | grep pcpu
> 	0000000000000000 D __pcpu_unique_ipv6_cookie_scratch
> 	bfd/net/ipv6$ nm ipv6.ko | grep pcpu
> 	(no result)

So, those __pcpu_unique and __pcpu_scope variables are only used so
that multiple copy of them collide with each other and trigger compile
failure (as the actual percpu variable needs to be declared __weak).
They're all put into .discard section, so should go away once it
passes through the linker.  gold left reference to that symbol while
discarding the definition.  Hmmm... different interpretation of
.discard?  Still weird tho.  There's nothing dereferencing that
symbol.

Thanks.

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