From: kernel test robot <lkp@intel.com>
To: Luis Henriques <luis@igalia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Miklos Szeredi <mszeredi@redhat.com>
Subject: fs/fuse/dir.c:38:21: sparse: sparse: symbol 'dentry_tree_work' was not declared. Should it be static?
Date: Fri, 08 May 2026 19:47:37 +0800 [thread overview]
Message-ID: <202605081928.WWMrMNOu-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 917719c412c48687d4a176965d1fa35320ec457c
commit: ab84ad5973869a660ca3ad0c54a2b84d975d47c4 fuse: new work queue to periodically invalidate expired dentries
date: 6 months ago
config: powerpc-randconfig-r122-20260508 (https://download.01.org/0day-ci/archive/20260508/202605081928.WWMrMNOu-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260508/202605081928.WWMrMNOu-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: ab84ad597386 ("fuse: new work queue to periodically invalidate expired dentries")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202605081928.WWMrMNOu-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/fuse/dir.c:38:21: sparse: sparse: symbol 'dentry_tree_work' was not declared. Should it be static?
vim +/dentry_tree_work +38 fs/fuse/dir.c
34
35 #define HASH_BITS 5
36 #define HASH_SIZE (1 << HASH_BITS)
37 static struct dentry_bucket dentry_hash[HASH_SIZE];
> 38 struct delayed_work dentry_tree_work;
39
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-08 11:48 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=202605081928.WWMrMNOu-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luis@igalia.com \
--cc=mszeredi@redhat.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