linux-kernel - Re: [PATCH 8/9] um: fix strrchr problems

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:	Tue, 30 Aug 2011 03:48:53 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Richard Weinberger <richard@....at>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	user-mode-linux-devel@...ts.sourceforge.net,
	Al Viro <viro@....linux.org.uk>
Subject: Re: [PATCH 8/9] um: fix strrchr problems

On Tue, Aug 30, 2011 at 01:23:31AM +0100, Al Viro wrote:
> On Tue, Aug 30, 2011 at 12:25:25AM +0200, Richard Weinberger wrote:
> 
> > I'm building most of the time static.
> > Using defconfig and
> > CONFIG_STATIC_LINK=y
> > it builds fine here (x86_64 and i386)
> 
> 32bit build works, 64bit one breaks with
> 
> /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../../lib/libc.a(strrchr.o): In function `rindex':
> (.text+0x0): multiple definition of `strrchr'
> 
> on squeeze/amd64 with stock toolchain and libc (2.11.2-10).  .config, if
> you care, is as below, but I really suspect that most of that is irrelevant.

As the matter of fact, on the same build system defconfig + STATIC_LINK +
UML_NET_VDE is enough to reproduce it.

Toolchain:
	libc6		2.11.2-10
	vde2		2.2.3-3
	gcc		4.4.5-8
	binutils	2.20.1-16

all from stock stable/amd64.  Note that debian has the original of that
patch in their user-mode-linux package; see http://bugs.debian.org/494995
for history.
--
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/