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: <20141016012840.GA7943@gondor.apana.org.au>
Date:	Thu, 16 Oct 2014 09:28:40 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	Jim Davis <jim.epost@...il.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next <linux-next@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"David S. Miller" <davem@...emloft.net>,
	linux-crypto <linux-crypto@...r.kernel.org>
Subject: Re: randconfig build error with next-20141015, in crypto

On Wed, Oct 15, 2014 at 04:24:20PM -0700, Jim Davis wrote:
> This looks like a similar problem to one reported in August
> (https://lists.01.org/pipermail/kbuild-all/2014-August/006021.html),
> but there are significantly more errors this time.   Random
> configuration file attached:
> 
> crypto/built-in.o: In function `crypto_ctr_free':
> ctr.c:(.text+0x41): undefined reference to `crypto_drop_spawn'

Something is wrong with your test because your config file is
inconsistent with the current Kconfig description.  In particular,
you've got CRYPTO_CTR=y and CRYPTO_BLKCIPHER=m and yet in our
Kconfig CRYPTO_CTR explicitly selects CRYPTO_BLKCIPHER.

If you're just doing a simple make then this could be a bug in the
kbuild system.

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
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