From: kernel test robot <lkp@intel.com>
To: Bradley Morgan <brads@mainlining.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: [paulmck-rcu:dev.2026.09.18a 24/34] block.c:undefined reference to `cmpxchg_emu_u8'
Date: Wed, 30 Sep 2026 11:13:04 +0800 [thread overview]
Message-ID: <202609301117.nVKrDSkb-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git dev.2026.09.18a
head: 90599c372e13369d11f6c1a01ff0094b16f72cf8
commit: c98d10b438b5626edb3f4e06f4f62bcb6ed6fe90 [24/34] lib: Add two-byte cmpxchg emulation function
config: xtensa-randconfig-1000-20260929 (https://download.01.org/0day-ci/archive/20260930/202609301117.nVKrDSkb-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260930/202609301117.nVKrDSkb-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202609301117.nVKrDSkb-lkp@intel.com/
All errors (new ones prefixed by >>):
xtensa-linux-ld: fs/crypto/block.o: in function `fscrypt_limit_io_blocks':
>> block.c:(.text+0x300): undefined reference to `cmpxchg_emu_u8'
xtensa-linux-ld: fs/crypto/block.o: in function `fscrypt_zeroout_range_end_io':
block.c:(.text+0x31c): undefined reference to `cmpxchg_emu_u8'
xtensa-linux-ld: fs/btrfs/bio.o: in function `btrfs_bio_alloc':
>> bio.c:(.text+0x88c): undefined reference to `cmpxchg_emu_u8'
xtensa-linux-ld: fs/btrfs/bio.o: in function `btrfs_bio_end_io':
bio.c:(.text+0x8e8): undefined reference to `cmpxchg_emu_u8'
`.exit.text' referenced in section `__jump_table' of drivers/staging/vme_user/vme_fake.o: defined in discarded section `.exit.text' of drivers/staging/vme_user/vme_fake.o
`.exit.text' referenced in section `__jump_table' of drivers/staging/vme_user/vme_fake.o: defined in discarded section `.exit.text' of drivers/staging/vme_user/vme_fake.o
xtensa-linux-ld: block/blk-crypto-fallback.o: in function `blk_crypto_fallback_decrypt_endio':
>> blk-crypto-fallback.c:(.text+0x10c): undefined reference to `cmpxchg_emu_u8'
xtensa-linux-ld: block/blk-crypto-fallback.o:blk-crypto-fallback.c:(.text+0x18c): more undefined references to `cmpxchg_emu_u8' follow
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-30 3:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 3:13 kernel test robot [this message]
2026-09-30 3:32 ` Paul E. McKenney
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=202609301117.nVKrDSkb-lkp@intel.com \
--to=lkp@intel.com \
--cc=brads@mainlining.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paulmck@kernel.org \
/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
all inboxes | Powered by JetHome®