From: kernel test robot <lkp@intel.com>
To: Nick Terrell <terrelln@meta.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 10035/10049] riscv32-linux-ld: section .data LMA [0007d000,004ed977] overlaps section .exit.text LMA [0007ccec,00085cff]
Date: Tue, 2 Jul 2024 22:17:00 +0800 [thread overview]
Message-ID: <202407022220.FK3vNexE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 82e4255305c554b0bb18b7ccf2db86041b4c8b6e
commit: 146199ecf450a5d50517986a74901b0f8de61866 [10035/10049] Merge branch 'zstd-next' of https://github.com/terrelln/linux.git
config: riscv-randconfig-r002-20230330 (https://download.01.org/0day-ci/archive/20240702/202407022220.FK3vNexE-lkp@intel.com/config)
compiler: riscv32-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240702/202407022220.FK3vNexE-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/202407022220.FK3vNexE-lkp@intel.com/
All errors (new ones prefixed by >>):
>> riscv32-linux-ld: section .data LMA [0007d000,004ed977] overlaps section .exit.text LMA [0007ccec,00085cff]
>> riscv32-linux-ld: section .text LMA [00085d00,01a7253b] overlaps section .data LMA [0007d000,004ed977]
riscv32-linux-ld: section __bug_table LMA [004ed978,0050e617] overlaps section .text LMA [00085d00,01a7253b]
riscv32-linux-ld: section .pci_fixup VMA [c201b0c0,c201dcef] overlaps section .data VMA [c2000000,c2470977]
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-02 14:17 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=202407022220.FK3vNexE-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=terrelln@meta.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