From: kernel test robot <lkp@intel.com>
To: Yury Norov <yury.norov@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>,
Kees Cook <kees@kernel.org>,
Nathan Chancellor <nathan@kernel.org>
Subject: kernel/sched/build_utility.o: warning: objtool: sched_is_eas_possible.isra.0+0x8c: stack state mismatch: reg1[28]=-1+0 reg2[28]=-2-56
Date: Sat, 7 Dec 2024 04:41:12 +0800 [thread overview]
Message-ID: <202412070437.ZjWaJvb1-lkp@intel.com> (raw)
Hi Yury,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: b8f52214c61a5b99a54168145378e91b40d10c90
commit: fda1dd3c54ef3c4200c2e77634a91610da973950 find: Switch from inline to __always_inline
date: 4 months ago
config: loongarch-randconfig-001-20241207 (https://download.01.org/0day-ci/archive/20241207/202412070437.ZjWaJvb1-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241207/202412070437.ZjWaJvb1-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/202412070437.ZjWaJvb1-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/sched/build_utility.o: warning: objtool: sched_is_eas_possible.isra.0+0x8c: stack state mismatch: reg1[28]=-1+0 reg2[28]=-2-56
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-06 20:41 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=202412070437.ZjWaJvb1-lkp@intel.com \
--to=lkp@intel.com \
--cc=briannorris@chromium.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yury.norov@gmail.com \
/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