From: kernel test robot <lkp@intel.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Huacai Chen <chenhuacai@kernel.org>,
Jinyang He <hejinyang@loongson.cn>,
Youling Tang <tangyouling@loongson.cn>
Subject: arch/loongarch/kernel/alternative.o: warning: objtool: apply_alternatives+0xa0: unreachable instruction
Date: Mon, 22 Jul 2024 12:38:31 +0800 [thread overview]
Message-ID: <202407221208.6SSBeN9H-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 7846b618e0a4c3e08888099d1d4512722b39ca99
commit: cb8a2ef0848ca80d67d6d56e2df757cfdf6b3355 LoongArch: Add ORC stack unwinder support
date: 4 months ago
config: loongarch-randconfig-001-20240722 (https://download.01.org/0day-ci/archive/20240722/202407221208.6SSBeN9H-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240722/202407221208.6SSBeN9H-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/202407221208.6SSBeN9H-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/9p/vfs_file.o: warning: objtool: v9fs_file_do_lock+0x64: unreachable instruction
--
>> fs/iomap/buffered-io.o: warning: objtool: iomap_write_begin+0x80: unreachable instruction
--
>> kernel/cgroup/cgroup.o: warning: objtool: compare_css_sets+0xc8: unreachable instruction
>> kernel/cgroup/cgroup.o: warning: objtool: cgroup_setup_root+0x2dc: unreachable instruction
>> kernel/cgroup/cgroup.o: warning: objtool: cgroup_destroy_root+0x4c: unreachable instruction
>> kernel/cgroup/cgroup.o: warning: objtool: cgroup_init_subsys+0x98: unreachable instruction
>> kernel/cgroup/cgroup.o: warning: objtool: cgroup_init+0x50: unreachable instruction
--
drivers/target/target_core_transport.c: In function 'transport_dump_vpd_ident':
drivers/target/target_core_transport.c:1263:59: warning: '%s' directive output may be truncated writing up to 253 bytes into a region of size 221 [-Wformat-truncation=]
1263 | "T10 VPD ASCII Device Identifier: %s\n",
| ^~
drivers/target/target_core_transport.c:1262:17: note: 'snprintf' output between 35 and 288 bytes into a destination of size 254
1262 | snprintf(buf, sizeof(buf),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
1263 | "T10 VPD ASCII Device Identifier: %s\n",
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1264 | &vpd->device_identifier[0]);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/target/target_core_transport.c:1268:59: warning: '%s' directive output may be truncated writing up to 253 bytes into a region of size 221 [-Wformat-truncation=]
1268 | "T10 VPD UTF-8 Device Identifier: %s\n",
| ^~
drivers/target/target_core_transport.c:1267:17: note: 'snprintf' output between 35 and 288 bytes into a destination of size 254
1267 | snprintf(buf, sizeof(buf),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
1268 | "T10 VPD UTF-8 Device Identifier: %s\n",
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1269 | &vpd->device_identifier[0]);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/target/target_core_transport.c:1258:60: warning: '%s' directive output may be truncated writing up to 253 bytes into a region of size 220 [-Wformat-truncation=]
1258 | "T10 VPD Binary Device Identifier: %s\n",
| ^~
drivers/target/target_core_transport.c:1257:17: note: 'snprintf' output between 36 and 289 bytes into a destination of size 254
1257 | snprintf(buf, sizeof(buf),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
1258 | "T10 VPD Binary Device Identifier: %s\n",
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1259 | &vpd->device_identifier[0]);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/target/target_core_transport.o: warning: objtool: target_init_cmd+0x60: unreachable instruction
--
>> drivers/base/regmap/regmap-irq.o: warning: objtool: regmap_irq_thread+0x2bc: unreachable instruction
--
>> drivers/mtd/nand/raw/nand_base.o: warning: objtool: nand_fill_oob+0xa4: unreachable instruction
>> drivers/mtd/nand/raw/nand_base.o: warning: objtool: nand_transfer_oob+0x94: unreachable instruction
--
>> drivers/mtd/nand/raw/nand_bbt.o: warning: objtool: verify_bbt_descr+0x78: unreachable instruction
--
>> fs/f2fs/inode.o: warning: objtool: __f2fs_crc32.isra.0+0x54: unreachable instruction
>> fs/f2fs/inode.o: warning: objtool: f2fs_evict_inode+0x110: unreachable instruction
--
>> fs/f2fs/node.o: warning: objtool: set_node_addr+0xc0: unreachable instruction
>> fs/f2fs/node.o: warning: objtool: __flush_nat_entry_set.isra.0+0x170: unreachable instruction
>> fs/f2fs/node.o: warning: objtool: f2fs_truncate_inode_blocks+0x250: unreachable instruction
>> fs/f2fs/node.o: warning: objtool: f2fs_alloc_nid+0xc4: unreachable instruction
>> fs/f2fs/node.o: warning: objtool: f2fs_alloc_nid_failed+0x60: unreachable instruction
>> fs/f2fs/node.o: warning: objtool: f2fs_destroy_node_manager+0xcc: unreachable instruction
--
>> fs/f2fs/segment.o: warning: objtool: get_new_segment+0x14c: unreachable instruction
>> fs/f2fs/segment.o: warning: objtool: current_sit_addr.isra.0+0x50: unreachable instruction
>> fs/f2fs/segment.o: warning: objtool: __locate_dirty_segment+0x11c: unreachable instruction
>> fs/f2fs/segment.o: warning: objtool: update_sit_entry+0x15c: unreachable instruction
>> fs/f2fs/segment.o: warning: objtool: __submit_discard_cmd+0x1f4: unreachable instruction
>> fs/f2fs/segment.o: warning: objtool: __issue_discard_cmd+0x15c: unreachable instruction
>> fs/f2fs/segment.o: warning: objtool: f2fs_allocate_data_block+0x124: unreachable instruction
>> fs/f2fs/segment.o: warning: objtool: f2fs_do_replace_block+0x254: unreachable instruction
>> fs/f2fs/segment.o: warning: objtool: f2fs_flush_sit_entries+0x340: unreachable instruction
--
fs/f2fs/data.o: warning: objtool: f2fs_submit_write_bio+0xe8: unreachable instruction
>> fs/f2fs/data.o: warning: objtool: f2fs_merge_page_bio+0x1a4: unreachable instruction
..
objdump-func vmlinux.o apply_alternatives:
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-07-22 4:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 4:38 kernel test robot [this message]
2024-07-22 8:57 ` arch/loongarch/kernel/alternative.o: warning: objtool: apply_alternatives+0xa0: unreachable instruction Tiezhu Yang
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=202407221208.6SSBeN9H-lkp@intel.com \
--to=lkp@intel.com \
--cc=chenhuacai@kernel.org \
--cc=hejinyang@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tangyouling@loongson.cn \
--cc=yangtiezhu@loongson.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.