From: kernel test robot <lkp@intel.com>
Cc: kbuild-all@lists.01.org, llvm@lists.linux.dev
Subject: [asahilinux:pr/22 78/189] kernel/reboot.o: warning: objtool: sys_off_handler_power_off()+0x150: sibling call from callable instruction with modified stack frame
Date: Tue, 26 Apr 2022 18:02:44 +0800 [thread overview]
Message-ID: <202204261746.I2rVRVV6-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: linux-kernel@vger.kernel.org
TO: Dmitry Osipenko <digetx@gmail.com>
CC: Hector Martin <marcan@marcan.st>
Hi Dmitry,
FYI, the error/warning still remains.
tree: https://github.com/AsahiLinux/linux pr/22
head: 7ee315306d1a3b0da8cf2a53e7f55889d0e7f034
commit: ec159207530d80c0a0bd04c1ac94db5766bbc3c0 [78/189] kernel: Add combined power-off+restart handler call chain API
config: x86_64-randconfig-a001-20220425 (https://download.01.org/0day-ci/archive/20220426/202204261746.I2rVRVV6-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 1cddcfdc3c683b393df1a5c9063252eb60e52818)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/AsahiLinux/linux/commit/ec159207530d80c0a0bd04c1ac94db5766bbc3c0
git remote add asahilinux https://github.com/AsahiLinux/linux
git fetch --no-tags asahilinux pr/22
git checkout ec159207530d80c0a0bd04c1ac94db5766bbc3c0
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> kernel/reboot.o: warning: objtool: sys_off_handler_power_off()+0x150: sibling call from callable instruction with modified stack frame
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-26 10: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=202204261746.I2rVRVV6-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@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