From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [linux-next:master 10134/10559] ld.lld: error: vmlinux.a(io_uring/rsrc.o):(function io_rsrc_node_alloc: .text+0x1ea): relocation R_RISCV_HI20 out of range: 527998 is not in [-524288, 524287]; references 'random_kmalloc_seed'
Date: Fri, 8 Nov 2024 19:35:22 +0800 [thread overview]
Message-ID: <202411081905.ylTejbtc-lkp@intel.com> (raw)
TO: Chuck Lever <chuck.lever@oracle.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 929beafbe7acce3267c06115e13e03ff6e50548a
commit: 6eb5109a27ed8698809c3bf5acb5df0a579f0095 [10134/10559] Merge branch 'nfsd-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
config: riscv-randconfig-001-20241108 (https://download.01.org/0day-ci/archive/20241108/202411081905.ylTejbtc-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 592c0fe55f6d9a811028b5f3507be91458ab2713)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241108/202411081905.ylTejbtc-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/202411081905.ylTejbtc-lkp@intel.com/
Note: the linux-next/master HEAD 929beafbe7acce3267c06115e13e03ff6e50548a builds fine.
It may have been fixed somewhere.
All errors (new ones prefixed by >>):
>> ld.lld: error: vmlinux.a(io_uring/rsrc.o):(function io_rsrc_node_alloc: .text+0x1ea): relocation R_RISCV_HI20 out of range: 527998 is not in [-524288, 524287]; references 'random_kmalloc_seed'
>>> referenced by atomic-arch-fallback.h:0 (include/linux/atomic/atomic-arch-fallback.h:0)
>>> defined in vmlinux.a(mm/slab_common.o)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-08 11:36 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=202411081905.ylTejbtc-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--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