From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Julia Lawall <julia.lawall@inria.fr>
Subject: arch/x86/kernel/smpboot.c:1040:6-7: ERROR: iterator variable bound on line 1039 cannot be NULL
Date: Thu, 28 Mar 2024 06:02:02 +0800 [thread overview]
Message-ID: <202403280539.R5tAQ3TJ-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Thomas Gleixner <tglx@linutronix.de>
CC: "Borislav Petkov (AMD)" <bp@alien8.de>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 962490525cffee6270422206c9d5bdb12d472c2b
commit: c90399fbd74a0713d5972a6d931e4a9918621e88 x86/cpu: Ensure that CPU info updates are propagated on UP
date: 4 days ago
:::::: branch date: 5 hours ago
:::::: commit date: 4 days ago
config: x86_64-randconfig-102-20240327 (https://download.01.org/0day-ci/archive/20240328/202403280539.R5tAQ3TJ-lkp@intel.com/config)
compiler: gcc-12 (Ubuntu 12.3.0-9ubuntu2) 12.3.0
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>
| Reported-by: Julia Lawall <julia.lawall@inria.fr>
| Closes: https://lore.kernel.org/r/202403280539.R5tAQ3TJ-lkp@intel.com/
cocci warnings: (new ones prefixed by >>)
>> arch/x86/kernel/smpboot.c:1040:6-7: ERROR: iterator variable bound on line 1039 cannot be NULL
vim +1040 arch/x86/kernel/smpboot.c
8aef135c73436fa Glauber de Oliveira Costa 2008-03-19 1033
ce2612b6706b4d0 Boris Ostrovsky 2021-11-02 1034 void __init smp_prepare_cpus_common(void)
8aef135c73436fa Glauber de Oliveira Costa 2008-03-19 1035 {
7ad728f98162cb1 Rusty Russell 2009-03-13 1036 unsigned int i;
7ad728f98162cb1 Rusty Russell 2009-03-13 1037
c90399fbd74a071 Thomas Gleixner 2024-03-22 1038 /* Mark all except the boot CPU as hotpluggable */
c90399fbd74a071 Thomas Gleixner 2024-03-22 @1039 for_each_possible_cpu(i) {
c90399fbd74a071 Thomas Gleixner 2024-03-22 @1040 if (i)
c90399fbd74a071 Thomas Gleixner 2024-03-22 1041 per_cpu(cpu_info.cpu_index, i) = nr_cpu_ids;
c90399fbd74a071 Thomas Gleixner 2024-03-22 1042 }
bd22a2f1982fa3e Tejun Heo 2011-01-23 1043
7ad728f98162cb1 Rusty Russell 2009-03-13 1044 for_each_possible_cpu(i) {
79f5599772ac2f1 Li Zefan 2009-06-15 1045 zalloc_cpumask_var(&per_cpu(cpu_sibling_map, i), GFP_KERNEL);
79f5599772ac2f1 Li Zefan 2009-06-15 1046 zalloc_cpumask_var(&per_cpu(cpu_core_map, i), GFP_KERNEL);
2e4c54dac7b360c Len Brown 2019-05-13 1047 zalloc_cpumask_var(&per_cpu(cpu_die_map, i), GFP_KERNEL);
b3d7336db553d31 Yinghai Lu 2011-01-21 1048 zalloc_cpumask_var(&per_cpu(cpu_llc_shared_map, i), GFP_KERNEL);
66558b730f2533c Tim Chen 2021-09-24 1049 zalloc_cpumask_var(&per_cpu(cpu_l2c_shared_map, i), GFP_KERNEL);
7ad728f98162cb1 Rusty Russell 2009-03-13 1050 }
8f37961cf22304f Tim Chen 2016-09-21 1051
8aef135c73436fa Glauber de Oliveira Costa 2008-03-19 1052 set_cpu_sibling_map(0);
ce2612b6706b4d0 Boris Ostrovsky 2021-11-02 1053 }
ce2612b6706b4d0 Boris Ostrovsky 2021-11-02 1054
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-03-27 22:02 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=202403280539.R5tAQ3TJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=julia.lawall@inria.fr \
--cc=oe-kbuild@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;
as well as URLs for NNTP newsgroup(s).