From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 6853/8213] csky-linux-ld: rotate.c:undefined reference to `__generic_xchg_called_with_bad_pointer'
Date: Sun, 17 Dec 2023 10:26:03 +0800 [thread overview]
Message-ID: <202312171007.c8vKL1Og-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 17cb8a20bde66a520a2ca7aad1063e1ce7382240
commit: ba97d6b747f2d1e78346a4f996c303d3e5a7a4f2 [6853/8213] afs: Fix fileserver rotation
config: csky-randconfig-r025-20220908 (https://download.01.org/0day-ci/archive/20231217/202312171007.c8vKL1Og-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231217/202312171007.c8vKL1Og-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/202312171007.c8vKL1Og-lkp@intel.com/
All errors (new ones prefixed by >>):
csky-linux-ld: fs/afs/callback.o: in function `__afs_break_callback':
include/asm-generic/cmpxchg.h:76:(.text+0xa34): undefined reference to `__generic_xchg_called_with_bad_pointer'
csky-linux-ld: fs/afs/callback.o: in function `__afs_break_callback':
fs/afs/callback.c:99:(.text+0xaec): undefined reference to `__generic_xchg_called_with_bad_pointer'
csky-linux-ld: fs/afs/rotate.o: in function `afs_start_fs_iteration':
rotate.c:(.text+0x664): undefined reference to `__generic_xchg_called_with_bad_pointer'
>> csky-linux-ld: rotate.c:(.text+0x70c): undefined reference to `__generic_xchg_called_with_bad_pointer'
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-17 2:26 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=202312171007.c8vKL1Og-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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