All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Jim Cromie" <jim.cromie@gmail.com>,
	" Łukasz Bartosik" <ukaszb@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jimc:folio-pool-v2-lockdep 14/21] kernel/locking/lockdep.c:587:1: sparse: sparse: symbol 'lockdep_trace_scratchpad_key' was not declared. Should it be static?
Date: Wed, 19 Aug 2026 14:20:28 +0800	[thread overview]
Message-ID: <202608191417.fTJXmNEy-lkp@intel.com> (raw)

tree:   https://github.com/jimc/linux.git folio-pool-v2-lockdep
head:   b6042163d72458308afa7eef95a3293507a1538e
commit: 198cb0234063750d4125d2f5b3fd29f373fba200 [14/21] locking/lockdep: Migrate and compact stack trace entries into folio_scratchpad
config: x86_64-randconfig-122-20260819 (https://download.01.org/0day-ci/archive/20260819/202608191417.fTJXmNEy-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260819/202608191417.fTJXmNEy-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/202608191417.fTJXmNEy-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   kernel/locking/lockdep.c:63:1: sparse: sparse: symbol 'lockdep_pool_key' was not declared. Should it be static?
>> kernel/locking/lockdep.c:587:1: sparse: sparse: symbol 'lockdep_trace_scratchpad_key' was not declared. Should it be static?
   kernel/locking/lockdep.c:3517:49: sparse: sparse: cast truncates bits from constant value (50000 becomes 0)
   kernel/locking/lockdep.c:3517:49: sparse: sparse: cast truncates bits from constant value (50000 becomes 0)

vim +/lockdep_trace_scratchpad_key +587 kernel/locking/lockdep.c

   586	
 > 587	DEFINE_STATIC_KEY_TRUE(lockdep_trace_scratchpad_key);
   588	static struct folio_scratchpad lockdep_trace_scratchpad =
   589		FOLIO_SCRATCHPAD_INIT_KEY(lockdep_trace_scratchpad,
   590					  FOLIO_POOL_64K_ORDER,
   591					  &lockdep_trace_scratchpad_key);
   592	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-08-19  6:20 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=202608191417.fTJXmNEy-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jim.cromie@gmail.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ukaszb@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.