linux-kernel - Re: linux-next: Tree for Mar 15 (crypto)

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: <20120315220534.81435da1cs6o2fks@www.81.fi>
Date:	Thu, 15 Mar 2012 22:05:34 +0200
From:	Jussi Kivilinna <jussi.kivilinna@...et.fi>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	linux-crypto@...r.kernel.org
Subject: Re: linux-next: Tree for Mar 15 (crypto)

Quoting Randy Dunlap <rdunlap@...otime.net>:

> On 03/15/2012 12:59 AM, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> News: the build system (see below) has had its toolchains for most
>> architectures updated to gcc 4.6.3.  People might like to check the build
>> results and consider if this change has caused any problems.  There are
>> also a number of architectures that are building today for the first
>> time.  Thanks to Tony Breeds for his efforts in providing toolchains.
>>
>> Changes since 20120314:
>
>
> on x86_64:
>
> arch/x86/crypto/twofish-x86_64-3way.o: In function `fini':
> (.exit.text+0x0): multiple definition of `fini'
> arch/x86/crypto/camellia-x86_64.o:(.exit.text+0x0): first defined here
> arch/x86/crypto/twofish-x86_64-3way.o: In function `init':
> (.init.text+0x0): multiple definition of `init'
> arch/x86/crypto/camellia-x86_64.o:(.init.text+0x0): first defined here
>

Ah.. init()/fini() should be static functions but are not. I'll send  
patches soon. Thanks.

>
> Full randconfig file is attached.
>
>
> --
> ~Randy
>



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