From: kernel test robot <lkp@intel.com>
To: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: [linux-next:master 2214/4328] sm4-neon-glue.c:undefined reference to `sm4_expandkey'
Date: Thu, 14 Apr 2022 22:04:03 +0800 [thread overview]
Message-ID: <202204142151.5cJBAHP4-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 40354149f4d738dc3492d9998e45b3f02950369a
commit: 4f1aef9b806f58ef76fdac0b4d9cfab6e66aeef1 [2214/4328] crypto: arm64/sm4 - add ARMv8 NEON implementation
config: arm64-randconfig-r002-20220414 (https://download.01.org/0day-ci/archive/20220414/202204142151.5cJBAHP4-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=4f1aef9b806f58ef76fdac0b4d9cfab6e66aeef1
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 4f1aef9b806f58ef76fdac0b4d9cfab6e66aeef1
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=arm64 SHELL=/bin/bash
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 >>):
aarch64-linux-ld: Unexpected GOT/PLT entries detected!
aarch64-linux-ld: Unexpected run-time procedure linkages detected!
aarch64-linux-ld: kexec relocation code is too big or misaligned
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-glue.o: in function `sm4_setkey':
>> sm4-neon-glue.c:(.text+0x190): undefined reference to `sm4_expandkey'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-glue.o: in function `sm4_cbc_encrypt':
>> sm4-neon-glue.c:(.text+0x268): undefined reference to `sm4_crypt_block'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-glue.o: in function `sm4_cfb_decrypt':
sm4-neon-glue.c:(.text+0x65c): undefined reference to `sm4_crypt_block'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-glue.o: in function `sm4_cfb_encrypt':
sm4-neon-glue.c:(.text+0x7f0): undefined reference to `sm4_crypt_block'
>> aarch64-linux-ld: sm4-neon-glue.c:(.text+0x880): undefined reference to `sm4_crypt_block'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-glue.o: in function `sm4_ctr_crypt':
sm4-neon-glue.c:(.text+0xa94): undefined reference to `sm4_crypt_block'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o: in function `__sm4_neon_crypt_blk1_4':
>> (.text+0x4): undefined reference to `crypto_sm4_sbox'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `crypto_sm4_sbox' which may bind externally can not be used when making a shared object; recompile with -fPIC
(.text+0x4): dangerous relocation: unsupported relocation
>> aarch64-linux-ld: (.text+0x8): undefined reference to `crypto_sm4_sbox'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o: in function `sm4_neon_crypt_blk1_8':
(.text+0x284): undefined reference to `crypto_sm4_sbox'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `crypto_sm4_sbox' which may bind externally can not be used when making a shared object; recompile with -fPIC
(.text+0x284): dangerous relocation: unsupported relocation
aarch64-linux-ld: (.text+0x288): undefined reference to `crypto_sm4_sbox'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o: in function `sm4_neon_crypt_blk8':
(.text+0x6e4): undefined reference to `crypto_sm4_sbox'
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `crypto_sm4_sbox' which may bind externally can not be used when making a shared object; recompile with -fPIC
(.text+0x6e4): dangerous relocation: unsupported relocation
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o:(.text+0x6e8): more undefined references to `crypto_sm4_sbox' follow
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `crypto_sm4_sbox' which may bind externally can not be used when making a shared object; recompile with -fPIC
arch/arm64/crypto/sm4-neon-core.o: in function `sm4_neon_cbc_dec_blk8':
(.text+0xb04): dangerous relocation: unsupported relocation
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `crypto_sm4_sbox' which may bind externally can not be used when making a shared object; recompile with -fPIC
arch/arm64/crypto/sm4-neon-core.o: in function `sm4_neon_cfb_dec_blk8':
(.text+0xf5c): dangerous relocation: unsupported relocation
aarch64-linux-ld: arch/arm64/crypto/sm4-neon-core.o: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `crypto_sm4_sbox' which may bind externally can not be used when making a shared object; recompile with -fPIC
arch/arm64/crypto/sm4-neon-core.o: in function `sm4_neon_ctr_enc_blk8':
(.text+0x13b4): dangerous relocation: unsupported relocation
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-14 14:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202204142151.5cJBAHP4-lkp@intel.com \
--to=lkp@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=tianjia.zhang@linux.alibaba.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;
as well as URLs for NNTP newsgroup(s).