From: kernel test robot <lkp@intel.com>
To: Tiezhu Yang <yangtiezhu@loongson.cn>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org,
Josh Poimboeuf <jpoimboe@kernel.org>
Subject: block/bfq.o: warning: objtool: bfq_bfqq_expire+0x3a8: sibling call from callable instruction with modified stack frame
Date: Mon, 7 Jul 2025 06:13:49 +0800 [thread overview]
Message-ID: <202507070332.OZWZVjr0-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 1f988d0788f50d8464f957e793fab356e2937369
commit: e20ab7d454ee8d1e0e8b9ff73a7c87e84c666b2f LoongArch: Enable jump table for objtool
date: 4 months ago
config: loongarch-randconfig-001-20250707 (https://download.01.org/0day-ci/archive/20250707/202507070332.OZWZVjr0-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 61529d9e36fa86782a2458e6bdeedf7f376ef4b5)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250707/202507070332.OZWZVjr0-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/202507070332.OZWZVjr0-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> block/bfq.o: warning: objtool: bfq_bfqq_expire+0x3a8: sibling call from callable instruction with modified stack frame
>> block/bfq.o: warning: objtool: bfq_set_next_ioprio_data+0x54: sibling call from callable instruction with modified stack frame
>> block/bfq.o: warning: objtool: bfq_get_queue+0xbc: sibling call from callable instruction with modified stack frame
--
drivers/media/i2c/adv7842.c:396:19: warning: unused function 'cec_write_clr_set' [-Wunused-function]
396 | static inline int cec_write_clr_set(struct v4l2_subdev *sd, u8 reg, u8 mask, u8 val)
| ^~~~~~~~~~~~~~~~~
1 warning generated.
>> drivers/media/i2c/adv7842.o: warning: objtool: adv7842_g_register+0x48: sibling call from callable instruction with modified stack frame
>> drivers/media/i2c/adv7842.o: warning: objtool: adv7842_s_register+0x44: sibling call from callable instruction with modified stack frame
drivers/media/i2c/adv7842.o: warning: objtool: adv7842_query_dv_timings+0x254: sibling call from callable instruction with modified stack frame
drivers/media/i2c/adv7842.o: warning: objtool: select_input+0x3c: sibling call from callable instruction with modified stack frame
>> drivers/media/i2c/adv7842.o: warning: objtool: enable_input+0x3c: sibling call from callable instruction with modified stack frame
drivers/media/i2c/adv7842.o: warning: objtool: adv7842_s_routing+0x48: sibling call from callable instruction with modified stack frame
drivers/media/i2c/adv7842.o: warning: objtool: adv7842_querystd+0xc0: sibling call from callable instruction with modified stack frame
>> drivers/media/i2c/adv7842.o: warning: objtool: adv7842_set_format+0x70: sibling call from callable instruction with modified stack frame
>> drivers/media/i2c/adv7842.o: warning: objtool: adv7842_debugfs_if_read+0x84: sibling call from callable instruction with modified stack frame
drivers/media/i2c/adv7842.o: warning: objtool: adv7842_s_ctrl+0x6c: sibling call from callable instruction with modified stack frame
--
drivers/staging/gpib/ines/ines_gpib.c:29:23: warning: variable 'nec_priv' set but not used [-Wunused-but-set-variable]
29 | struct nec7210_priv *nec_priv;
| ^
drivers/staging/gpib/ines/ines_gpib.c:1123:21: warning: variable 'dev' set but not used [-Wunused-but-set-variable]
1123 | struct local_info *dev;
| ^
2 warnings generated.
>> drivers/staging/gpib/ines/ines_gpib.o: warning: objtool: ines_common_pci_attach+0x2ac: sibling call from callable instruction with modified stack frame
--
drivers/staging/gpib/cb7210/cb7210.c:383:23: warning: variable 'nec_priv' set but not used [-Wunused-but-set-variable]
383 | struct nec7210_priv *nec_priv;
| ^
drivers/staging/gpib/cb7210/cb7210.c:1264:24: warning: variable 'handle' set but not used [-Wunused-but-set-variable]
1264 | struct pcmcia_device *handle;
| ^
drivers/staging/gpib/cb7210/cb7210.c:1265:21: warning: variable 'dev' set but not used [-Wunused-but-set-variable]
1265 | struct local_info *dev;
| ^
3 warnings generated.
>> drivers/staging/gpib/cb7210/cb7210.o: warning: objtool: cb7210_accel_read+0x39c: sibling call from callable instruction with modified stack frame
>> drivers/staging/gpib/cb7210/cb7210.o: warning: objtool: cb7210_accel_write+0x15c: sibling call from callable instruction with modified stack frame
>> drivers/staging/gpib/cb7210/cb7210.o: warning: objtool: cb7210_init+0x80: sibling call from callable instruction with modified stack frame
>> drivers/staging/gpib/cb7210/cb7210.o: warning: objtool: cb_isa_attach+0xb0: sibling call from callable instruction with modified stack frame
--
drivers/video/fbdev/aty/aty128fb.c:534:18: warning: unused function '_aty_ld_8' [-Wunused-function]
534 | static inline u8 _aty_ld_8(unsigned int regindex,
| ^~~~~~~~~
1 warning generated.
>> drivers/video/fbdev/aty/aty128fb.o: warning: objtool: aty128_timings+0x1a8: sibling call from callable instruction with modified stack frame
drivers/video/fbdev/aty/aty128fb.o: warning: objtool: aty128fb_check_var+0xa4: sibling call from callable instruction with modified stack frame
>> drivers/video/fbdev/aty/aty128fb.o: warning: objtool: aty128fb_setcolreg+0xb4: sibling call from callable instruction with modified stack frame
>> drivers/video/fbdev/aty/aty128fb.o: warning: objtool: aty128fb_blank+0x5c: sibling call from callable instruction with modified stack frame
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-07-06 22:14 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=202507070332.OZWZVjr0-lkp@intel.com \
--to=lkp@intel.com \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®