From: "Chen, Rong A" <rong.a.chen@intel.com>
To: Alexander Potapenko <glider@google.com>,
kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
"Kees Cook" <keescook@chromium.org>,
"Maciej Żenczykowski" <maze@google.com>
Subject: Re: arch/powerpc/kexec/crash.c:311:22: error: variable 'i' might be clobbered by 'longjmp' or 'vfork'
Date: Fri, 4 Nov 2022 15:20:50 +0800 [thread overview]
Message-ID: <ad55edce-7929-a2b7-4882-9ab9789d76e0@intel.com> (raw)
In-Reply-To: <CAG_fn=VqT+ORnMwR=YCsp6SxOMESqL9-O_t8G-5BdsNNBe13Mg@mail.gmail.com>
On 10/31/2022 4:27 PM, Alexander Potapenko wrote:
> Looks unrelated to this 2-year old commit?
Hi Alexander,
Sorry for the inconvenience, the commit here is not the root cause for
this error, we'll add it to ignore list.
Best Regards,
Rong Chen
>
> On Sun, Oct 30, 2022 at 6:12 PM kernel test robot <lkp@intel.com> wrote:
>>
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>> head: 882ad2a2a8ffa1defecdf907052f04da2737dc46
>> commit: f0fe00d4972a8cd4b98cc2c29758615e4d51cdfe security: allow using Clang's zero initialization for stack variables
>> date: 2 years, 4 months ago
>> config: powerpc-wii_defconfig
>> compiler: powerpc-linux-gcc (GCC) 12.1.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/torvalds/linux.git/commit/?id=f0fe00d4972a8cd4b98cc2c29758615e4d51cdfe
>> git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> git fetch --no-tags linus master
>> git checkout f0fe00d4972a8cd4b98cc2c29758615e4d51cdfe
>> # save the config file
>> mkdir build_dir && cp config build_dir/.config
>> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross W=1 O=build_dir ARCH=powerpc SHELL=/bin/bash arch/powerpc/
>>
>> If you fix the issue, kindly add following tag where applicable
>> | Reported-by: kernel test robot <lkp@intel.com>
>>
>> All errors (new ones prefixed by >>):
>>
>> arch/powerpc/kexec/crash.c: In function 'default_machine_crash_shutdown':
>>>> arch/powerpc/kexec/crash.c:311:22: error: variable 'i' might be clobbered by 'longjmp' or 'vfork' [-Werror=clobbered]
>> 311 | unsigned int i;
>> | ^
>> cc1: all warnings being treated as errors
>>
>>
>> vim +311 arch/powerpc/kexec/crash.c
>>
>> 496b010e1e70a9 arch/powerpc/kernel/crash.c Michael Neuling 2008-01-18 308
>> cc53291521701f arch/powerpc/kernel/crash.c Michael Ellerman 2005-12-04 309 void default_machine_crash_shutdown(struct pt_regs *regs)
>> cc53291521701f arch/powerpc/kernel/crash.c Michael Ellerman 2005-12-04 310 {
>> 496b010e1e70a9 arch/powerpc/kernel/crash.c Michael Neuling 2008-01-18 @311 unsigned int i;
>>
>> :::::: The code at line 311 was first introduced by commit
>> :::::: 496b010e1e70a9b4286fa34f19523f24a194f119 [POWERPC] kdump shutdown hook support
>>
>> :::::: TO: Michael Neuling <mikey@neuling.org>
>> :::::: CC: Paul Mackerras <paulus@samba.org>
>>
>> --
>> 0-DAY CI Kernel Test Service
>> https://01.org/lkp
>
>
>
prev parent reply other threads:[~2022-11-04 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 17:11 kernel test robot
2022-10-31 8:27 ` Alexander Potapenko
2022-11-04 7:20 ` Chen, Rong A [this message]
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=ad55edce-7929-a2b7-4882-9ab9789d76e0@intel.com \
--to=rong.a.chen@intel.com \
--cc=glider@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=maze@google.com \
--cc=oe-kbuild-all@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
all inboxes | Powered by JetHome®