From: kernel test robot <lkp@intel.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: fs/pidfs.c:99:1: sparse: sparse: symbol 'pidfs_ino_lock' was not declared. Should it be static?
Date: Thu, 23 Jul 2026 15:15:48 +0800 [thread overview]
Message-ID: <202607231547.ehCQxi0L-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 4539944e515183668109bdf4d0c3d7d228383d88
commit: 87caaeef79950377b616f3ba2265a82742cb9583 pidfs: implement ino allocation without the pidmap lock
date: 5 months ago
config: i386-randconfig-062-20260723 (https://download.01.org/0day-ci/archive/20260723/202607231547.ehCQxi0L-lkp@intel.com/config)
compiler: clang version 22.1.3 (https://github.com/llvm/llvm-project e9846648fd6183ee6d8cbdb4502213fcf902a211)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260723/202607231547.ehCQxi0L-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
| Fixes: 87caaeef7995 ("pidfs: implement ino allocation without the pidmap lock")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202607231547.ehCQxi0L-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/pidfs.c:99:1: sparse: sparse: symbol 'pidfs_ino_lock' was not declared. Should it be static?
fs/pidfs.c:336:13: sparse: sparse: context imbalance in 'pidfd_info' - different lock contexts for basic block
fs/pidfs.c:931:5: sparse: sparse: context imbalance in 'pidfs_register_pid' - different lock contexts for basic block
vim +/pidfs_ino_lock +99 fs/pidfs.c
98
> 99 DEFINE_SPINLOCK(pidfs_ino_lock);
100 static u64 pidfs_ino_nr = 1;
101
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-23 7:19 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=202607231547.ehCQxi0L-lkp@intel.com \
--to=lkp@intel.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjguzik@gmail.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®