On Tue, Apr 05, 2016 at 07:15:21AM +0000, Li, Philip wrote: > > > > -----Original Message----- > > From: Herbert Xu [mailto:herbert@xxxxxxxxxxxxxxxxxxx] > > Sent: Monday, April 4, 2016 10:00 PM > > To: Wu, Fengguang <fengguang.wu@xxxxxxxxx> > > Cc: Sabrina Dubroca <sd@xxxxxxxxxxxxxxx>; kbuild-all@xxxxxx; > > linux-kernel@xxxxxxxxxxxxxxx; Hannes Frederic Sowa > > <hannes@xxxxxxxxxxxxxxxxxxx>; Linux Crypto Mailing List > > <linux-crypto@xxxxxxxxxxxxxxx> > > Subject: Re: gcm.c:undefined reference to `crypto_aead_setauthsize' > > > > On Fri, Apr 01, 2016 at 03:02:30PM +0000, kbuild test robot wrote: > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git > > master > > > head: 6ddf37da05cd71bf9e43349d607e810b43c9008a > > > commit: c09440f7dcb304002dfced8c0fea289eb25f2da0 macsec: introduce > > IEEE 802.1AE driver > > > date: 3 weeks ago > > > config: x86_64-randconfig-s3-04012139 (attached as .config) > > > reproduce: > > > git checkout c09440f7dcb304002dfced8c0fea289eb25f2da0 > > > # save the attached .config to linux build tree > > > make ARCH=x86_64 > > > > > > All errors (new ones prefixed by >>): > > > > > > crypto/built-in.o: In function `gcm_enc_copy_hash': > > > >> gcm.c:(.text+0x278): undefined reference to `crypto_xor' > > > > GCM is y but AEAD is only m, yet GCM selects AEAD. Perhaps a kbuild bug? > Thanks Herbert, currently we use make randconfig to generate this kconfig file, is it possible this is still a valid settings? Sorry I didn't mean kbuild as in your build system, but kbuild as in the kernel kbuild subsystem. AFAICS, the Kconfig rules should forbid the situation in your config file where GCM=y but AEAD=m because GCM selects AEAD. So the fact that it happened either means that there is something that I am missing or that the kbuild subsystem is buggy. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> 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-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
