From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [morimoto:sound-cleanup-2024-11-08 42/70] ld.lld: error: vmlinux.a(io_uring/tctx.o):(function __io_uring_add_tctx_node: .text+0x8e): relocation R_RISCV_HI20 out of range: 527995 is not in [-524288, 524287]; references 'random_kmalloc_seed'
Date: Sat, 9 Nov 2024 00:03:15 +0800 [thread overview]
Message-ID: <202411082328.HX2SQZ3b-lkp@intel.com> (raw)
TO: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
tree: https://github.com/morimoto/linux sound-cleanup-2024-11-08
head: e9ab69de24b2818ae26f88e606ccea272bfa1705
commit: c26577ac5a361528b1ede028fa047bc10fa62274 [42/70] ASoC: sdw_utils: don't indicate duplicate error message
config: riscv-randconfig-001-20241108 (https://download.01.org/0day-ci/archive/20241108/202411082328.HX2SQZ3b-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/202411082328.HX2SQZ3b-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/202411082328.HX2SQZ3b-lkp@intel.com/
Note: the morimoto/sound-cleanup-2024-11-08 HEAD e9ab69de24b2818ae26f88e606ccea272bfa1705 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> ld.lld: error: vmlinux.a(io_uring/tctx.o):(function __io_uring_add_tctx_node: .text+0x8e): relocation R_RISCV_HI20 out of range: 527995 is not in [-524288, 524287]; references 'random_kmalloc_seed'
>>> referenced by tctx.c:53 (io_uring/tctx.c:53)
>>> 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 16: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=202411082328.HX2SQZ3b-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