From: kernel test robot <lkp@intel.com>
To: Marco Chiappero <marco.chiappero@intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
Tomaszx Kowalik <tomaszx.kowalik@intel.com>,
Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Subject: drivers/crypto/qat/qat_common/qat_algs.c:483: undefined reference to `aes_expandkey'
Date: Sat, 19 Dec 2020 17:51:50 +0800 [thread overview]
Message-ID: <202012191747.bZbGM1kx-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2086 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 3644e2d2dda78e21edd8f5415b6d7ab03f5f54f3
commit: 5106dfeaeabea73d5132daab1d89d57b57fa98b7 crypto: qat - add AES-XTS support for QAT GEN4 devices
date: 8 days ago
config: i386-randconfig-m021-20201216 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5106dfeaeabea73d5132daab1d89d57b57fa98b7
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 5106dfeaeabea73d5132daab1d89d57b57fa98b7
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: drivers/crypto/qat/qat_common/qat_algs.o: in function `qat_alg_xts_reverse_key':
>> drivers/crypto/qat/qat_common/qat_algs.c:483: undefined reference to `aes_expandkey'
vim +483 drivers/crypto/qat/qat_common/qat_algs.c
475
476 static void qat_alg_xts_reverse_key(const u8 *key_forward, unsigned int keylen,
477 u8 *key_reverse)
478 {
479 struct crypto_aes_ctx aes_expanded;
480 int nrounds;
481 u8 *key;
482
> 483 aes_expandkey(&aes_expanded, key_forward, keylen);
484 if (keylen == AES_KEYSIZE_128) {
485 nrounds = 10;
486 key = (u8 *)aes_expanded.key_enc + (AES_BLOCK_SIZE * nrounds);
487 memcpy(key_reverse, key, AES_BLOCK_SIZE);
488 } else {
489 /* AES_KEYSIZE_256 */
490 nrounds = 14;
491 key = (u8 *)aes_expanded.key_enc + (AES_BLOCK_SIZE * nrounds);
492 memcpy(key_reverse, key, AES_BLOCK_SIZE);
493 memcpy(key_reverse + AES_BLOCK_SIZE, key - AES_BLOCK_SIZE,
494 AES_BLOCK_SIZE);
495 }
496 }
497
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32469 bytes --]
next reply other threads:[~2020-12-19 9:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-19 9:51 kernel test robot [this message]
2020-12-19 18:23 kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202012191747.bZbGM1kx-lkp@intel.com \
--to=lkp@intel.com \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.chiappero@intel.com \
--cc=tomaszx.kowalik@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome