From: kernel test robot <lkp@intel.com>
To: Josh Poimboeuf <jpoimboe@redhat.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jpoimboe:objtool-run 11/29] arch/powerpc/kernel/smp.c:1781:1: warning: 'noreturn' function does return
Date: Thu, 14 Apr 2022 23:01:04 +0800 [thread overview]
Message-ID: <202204142253.7Hya9r42-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git objtool-run
head: 47d3f4f7a72524799c1f646713e2377e3c4e239f
commit: 685d8d205c29aa853326bd2bb27dcee2ba1f5ef4 [11/29] sched: Convert arch_cpu_idle_dead() to proper __noreturn
config: powerpc-allmodconfig (https://download.01.org/0day-ci/archive/20220414/202204142253.7Hya9r42-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 11.2.0
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://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git/commit/?id=685d8d205c29aa853326bd2bb27dcee2ba1f5ef4
git remote add jpoimboe https://git.kernel.org/pub/scm/linux/kernel/git/jpoimboe/linux.git
git fetch --no-tags jpoimboe objtool-run
git checkout 685d8d205c29aa853326bd2bb27dcee2ba1f5ef4
# save the config file to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=powerpc SHELL=/bin/bash arch/powerpc/kernel/
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 >>):
arch/powerpc/kernel/smp.c: In function 'arch_cpu_idle_dead':
>> arch/powerpc/kernel/smp.c:1781:1: warning: 'noreturn' function does return
1781 | }
| ^
vim +/noreturn +1781 arch/powerpc/kernel/smp.c
d0174c721900ff8 Nathan Fontenot 2010-01-14 1767
1ea21ba231f2480 Michael Ellerman 2020-08-19 1768 void arch_cpu_idle_dead(void)
1ea21ba231f2480 Michael Ellerman 2020-08-19 1769 {
424ef0160f439fe Naveen N. Rao 2018-04-19 1770 /*
424ef0160f439fe Naveen N. Rao 2018-04-19 1771 * Disable on the down path. This will be re-enabled by
424ef0160f439fe Naveen N. Rao 2018-04-19 1772 * start_secondary() via start_secondary_resume() below
424ef0160f439fe Naveen N. Rao 2018-04-19 1773 */
424ef0160f439fe Naveen N. Rao 2018-04-19 1774 this_cpu_disable_ftrace();
424ef0160f439fe Naveen N. Rao 2018-04-19 1775
39f87561454dc33 Michael Ellerman 2020-08-19 1776 if (smp_ops->cpu_offline_self)
39f87561454dc33 Michael Ellerman 2020-08-19 1777 smp_ops->cpu_offline_self();
fa3f82c8bb7acbe Benjamin Herrenschmidt 2011-02-10 1778
fa3f82c8bb7acbe Benjamin Herrenschmidt 2011-02-10 1779 /* If we return, we re-enter start_secondary */
fa3f82c8bb7acbe Benjamin Herrenschmidt 2011-02-10 1780 start_secondary_resume();
abb17f9c3a92c5a Milton Miller 2010-05-19 @1781 }
fa3f82c8bb7acbe Benjamin Herrenschmidt 2011-02-10 1782
:::::: The code at line 1781 was first introduced by commit
:::::: abb17f9c3a92c5acf30e749efdf0419b7f50a5b8 powerpc: Use common cpu_die (fixes SMP+SUSPEND build)
:::::: TO: Milton Miller <miltonm@bga.com>
:::::: CC: Benjamin Herrenschmidt <benh@kernel.crashing.org>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-04-14 15:45 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=202204142253.7Hya9r42-lkp@intel.com \
--to=lkp@intel.com \
--cc=jpoimboe@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
/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