Linux-mm Archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Joel Granados <j.granados@samsung.com>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 10455/10463] include/linux/blkdev.h:733:(.text+0x260): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR1'
Date: Fri, 3 May 2024 15:31:26 +0800	[thread overview]
Message-ID: <202405031559.2nHyrpwv-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   9c6ecb3cb6e20c4fd7997047213ba0efcf9ada1a
commit: 5070493a645c67e42b3e86b5cad9796e831281dc [10455/10463] Merge branch 'sysctl-next' of git://git.kernel.org/pub/scm/linux/kernel/git/sysctl/sysctl.git
config: riscv-randconfig-c023-20221031 (https://download.01.org/0day-ci/archive/20240503/202405031559.2nHyrpwv-lkp@intel.com/config)
compiler: riscv64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240503/202405031559.2nHyrpwv-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/202405031559.2nHyrpwv-lkp@intel.com/

All errors (new ones prefixed by >>):

   riscv64-linux-ld: section .data LMA [00000000012ee000,000000000215c197] overlaps section .text LMA [00000000000b7734,0000000002b4b903]
   riscv64-linux-ld: section .data..percpu LMA [00000000031e8000,0000000003206a5f] overlaps section .rodata LMA [0000000002b4db00,000000000326a2ad]
   riscv64-linux-ld: section .init.pi.text VMA [ffffffff82b4b904,ffffffff82b4da37] overlaps section .data VMA [ffffffff82000000,ffffffff82e6e197]
   riscv64-linux-ld: section .got VMA [ffffffff82e6e198,ffffffff82e6e1a7] overlaps section .rodata VMA [ffffffff82b4db00,ffffffff8326a2ad]
   riscv64-linux-ld: section .init.pi.rodata.str1.8 VMA [ffffffff8326a2b0,ffffffff8326a332] overlaps section .bss VMA [ffffffff82f61000,ffffffff83ef965f]
   block/genhd.o: in function `bdev_nr_sectors':
>> include/linux/blkdev.h:733:(.text+0x260): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR1'
   block/genhd.o: in function `genhd_device_init':
>> block/genhd.c:890:(.init.text+0xa): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR1'
   block/early-lookup.o: in function `devt_from_partuuid':
   block/early-lookup.c:71:(.init.text+0x188): relocation truncated to fit: R_RISCV_GPREL_I against symbol `block_class' defined in .rodata section in block/genhd.o
   drivers/clk/clk.o: in function `of_clk_src_onecell_get':
   drivers/clk/clk.c:4975:(.text+0x5bac): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR3'
   drivers/clk/clk.o: in function `trace_clk_unprepare':
   include/trace/events/clk.h:74:(.init.text+0x5b4): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR3'
   drivers/base/core.o: in function `memalloc_flags_restore':
   include/linux/sched/mm.h:355:(.text+0x46d6): relocation truncated to fit: R_RISCV_GPREL_I against symbol `block_class' defined in .rodata section in block/genhd.o
   drivers/base/devtmpfs.o: in function `devtmpfs_create_node':
   drivers/base/devtmpfs.c:131:(.text+0x98a): relocation truncated to fit: R_RISCV_GPREL_I against symbol `block_class' defined in .rodata section in block/genhd.o
   drivers/base/devtmpfs.o: in function `dev_mynode':
   drivers/base/devtmpfs.c:295:(.text.unlikely+0x1a0): relocation truncated to fit: R_RISCV_GPREL_I against symbol `block_class' defined in .rodata section in block/genhd.o
   block/blk-mq-tag.o: in function `kmalloc_node_noprof':
   include/linux/slab.h:677:(.text+0x4ace): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR1'
   block/blk-stat.o: in function `rcu_read_unlock':
   include/linux/rcupdate.h:868:(.text+0x127e): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR2'
   block/blk-mq-sysfs.o: in function `blk_mq_hw_sysfs_nr_reserved_tags_show':
   block/blk-mq-sysfs.c:79:(.text+0x52): additional relocation overflows omitted from the output


vim +733 include/linux/blkdev.h

322cbb50de7118 Christoph Hellwig 2022-01-24  730  
322cbb50de7118 Christoph Hellwig 2022-01-24  731  static inline sector_t bdev_nr_sectors(struct block_device *bdev)
322cbb50de7118 Christoph Hellwig 2022-01-24  732  {
322cbb50de7118 Christoph Hellwig 2022-01-24 @733  	return bdev->bd_nr_sectors;
322cbb50de7118 Christoph Hellwig 2022-01-24  734  }
322cbb50de7118 Christoph Hellwig 2022-01-24  735  

:::::: The code at line 733 was first introduced by commit
:::::: 322cbb50de711814c42fb088f6d31901502c711a block: remove genhd.h

:::::: TO: Christoph Hellwig <hch@lst.de>
:::::: CC: Jens Axboe <axboe@kernel.dk>

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki


             reply	other threads:[~2024-05-03  7:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20240503073224eucas1p1b05462c0509f4a1f45717986fd324d14@eucas1p1.samsung.com>
2024-05-03  7:31 ` kernel test robot [this message]
2024-05-03  9:10   ` [linux-next:master 10455/10463] include/linux/blkdev.h:733:(.text+0x260): relocation truncated to fit: R_RISCV_GPREL_I against `.LANCHOR1' Joel Granados

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=202405031559.2nHyrpwv-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=j.granados@samsung.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).