From: kernel test robot <lkp@intel.com>
To: Brian Gerst <brgerst@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>
Subject: arch/x86/kernel/cpu/common.c:2083:1: sparse: sparse: symbol '__pcpu_scope___x86_call_depth' was not declared. Should it be static?
Date: Sat, 17 Jan 2026 16:00:50 +0800 [thread overview]
Message-ID: <202601171524.PAxAbxhr-lkp@intel.com> (raw)
Hi Brian,
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: d3eeb99bbc99cc5eb94a4a75ed4415a0272254ef
commit: 839be1619fb897364b782997bc2c5d072d7a79f2 x86/retbleed: Move call depth to percpu hot section
date: 11 months ago
config: x86_64-randconfig-121-20260117 (https://download.01.org/0day-ci/archive/20260117/202601171524.PAxAbxhr-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260117/202601171524.PAxAbxhr-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/202601171524.PAxAbxhr-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/x86/kernel/cpu/common.c:2083:1: sparse: sparse: symbol '__pcpu_scope___x86_call_depth' was not declared. Should it be static?
vim +/__pcpu_scope___x86_call_depth +2083 arch/x86/kernel/cpu/common.c
2076
2077 #ifdef CONFIG_X86_64
2078 /*
2079 * Note: Do not make this dependant on CONFIG_MITIGATION_CALL_DEPTH_TRACKING
2080 * so that this space is reserved in the hot cache section even when the
2081 * mitigation is disabled.
2082 */
> 2083 DEFINE_PER_CPU_CACHE_HOT(u64, __x86_call_depth);
2084 EXPORT_PER_CPU_SYMBOL(__x86_call_depth);
2085
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-01-17 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 8:00 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-12-13 22:49 kernel test robot
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=202601171524.PAxAbxhr-lkp@intel.com \
--to=lkp@intel.com \
--cc=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--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®