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: lib/bch.o: warning: objtool: find_poly_roots+0x5ac: sibling call from callable instruction with modified stack frame
Date: Sat, 26 Jul 2025 06:02:04 +0200 [thread overview]
Message-ID: <202507260646.q8oawNxL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 5f33ebd2018ced2600b3fad2f8e2052498eb4072
commit: e20ab7d454ee8d1e0e8b9ff73a7c87e84c666b2f LoongArch: Enable jump table for objtool
date: 5 months ago
config: loongarch-randconfig-2004-20250726 (https://download.01.org/0day-ci/archive/20250726/202507260646.q8oawNxL-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project b4edd827e4f71c2a0fcb13f79de7eae4545f0aea)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250726/202507260646.q8oawNxL-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/202507260646.q8oawNxL-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> lib/bch.o: warning: objtool: find_poly_roots+0x5ac: sibling call from callable instruction with modified stack frame
--
drivers/input/touchscreen/mms114.c:507:15: warning: cast to smaller integer type 'enum mms_type' from 'const void *' [-Wvoid-pointer-to-enum-cast]
507 | data->type = (enum mms_type)match_data;
| ^~~~~~~~~~~~~~~~~~~~~~~~~
1 warning generated.
>> drivers/input/touchscreen/mms114.o: warning: objtool: mms114_start+0xb4: sibling call from callable instruction with modified stack frame
--
drivers/char/applicom.c:130:25: warning: variable 'byte_reset_it' set but not used [-Wunused-but-set-variable]
130 | volatile unsigned char byte_reset_it;
| ^
drivers/char/applicom.c:542:6: warning: variable 'ret' set but not used [-Wunused-but-set-variable]
542 | int ret = 0;
| ^
drivers/char/applicom.c:705:25: warning: variable 'byte_reset_it' set but not used [-Wunused-but-set-variable]
705 | volatile unsigned char byte_reset_it;
| ^
3 warnings generated.
>> drivers/char/applicom.o: warning: objtool: ac_ioctl+0x104: sibling call from callable instruction with modified stack frame
--
drivers/video/fbdev/matrox/g450_pll.c:410:18: warning: variable 'mnp' set but not used [-Wunused-but-set-variable]
410 | unsigned int mnp;
| ^
1 warning generated.
>> drivers/video/fbdev/matrox/g450_pll.o: warning: objtool: matroxfb_g450_setpll_cond+0x58: sibling call from callable instruction with modified stack frame
>> drivers/video/fbdev/matrox/g450_pll.o: warning: objtool: matroxfb_g450_setclk+0x98: sibling call from callable instruction with modified stack frame
>> drivers/video/fbdev/matrox/g450_pll.o: warning: objtool: g450_testpll+0x48: sibling call from callable instruction with modified stack frame
--
drivers/media/i2c/adv7604.c:432:19: warning: unused function 'cec_write_clr_set' [-Wunused-function]
432 | static inline int cec_write_clr_set(struct v4l2_subdev *sd, u8 reg, u8 mask,
| ^~~~~~~~~~~~~~~~~
1 warning generated.
>> drivers/media/i2c/adv7604.o: warning: objtool: read_stdi+0x3e4: sibling call from callable instruction with modified stack frame
>> drivers/media/i2c/adv7604.o: warning: objtool: adv76xx_set_edid+0x260: sibling call from callable instruction with modified stack frame
>> drivers/media/i2c/adv7604.o: warning: objtool: adv76xx_debugfs_if_read+0xc0: sibling call from callable instruction with modified stack frame
>> drivers/media/i2c/adv7604.o: warning: objtool: adv76xx_s_ctrl+0x64: 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-26 4:03 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=202507260646.q8oawNxL-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®