From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18-2026-04 14/14] fs/fuse/dir.c:365:13: warning: 'fuse_dentry_release' defined but not used
Date: Tue, 21 Jul 2026 21:49:06 +0800 [thread overview]
Message-ID: <202607212136.NJMMrW69-lkp@intel.com> (raw)
Hi Paul,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android17-6.18-2026-04
head: bbf6a2e83ab5d0b5043355d606cd75cc141d23a0
commit: be926e6761d28d105ba672242e81e911e0d7e5e0 [14/14] ANDROID: fuse-bpf: fuse-bpf v1.3
config: i386-randconfig-141-20260721 (https://download.01.org/0day-ci/archive/20260721/202607212136.NJMMrW69-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
smatch: v0.5.0-9187-g5189e3fb
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260721/202607212136.NJMMrW69-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/202607212136.NJMMrW69-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> fs/fuse/dir.c:365:13: warning: 'fuse_dentry_release' defined but not used [-Wunused-function]
365 | static void fuse_dentry_release(struct dentry *dentry)
| ^~~~~~~~~~~~~~~~~~~
>> fs/fuse/dir.c:358:12: warning: 'fuse_dentry_init' defined but not used [-Wunused-function]
358 | static int fuse_dentry_init(struct dentry *dentry)
| ^~~~~~~~~~~~~~~~
vim +/fuse_dentry_release +365 fs/fuse/dir.c
e5e5558e923f358 Miklos Szeredi 2005-09-09 356
be926e6761d28d1 Paul Lawrence 2021-12-02 357 #if BITS_PER_LONG < 64 || defined(CONFIG_FUSE_BPF)
f75fdf22b0a8470 Miklos Szeredi 2016-10-01 @358 static int fuse_dentry_init(struct dentry *dentry)
f75fdf22b0a8470 Miklos Szeredi 2016-10-01 359 {
be926e6761d28d1 Paul Lawrence 2021-12-02 360 dentry->d_fsdata = kzalloc(sizeof(struct fuse_dentry),
dc69e98c241e145 Khazhismel Kumykov 2019-09-17 361 GFP_KERNEL_ACCOUNT | __GFP_RECLAIMABLE);
f75fdf22b0a8470 Miklos Szeredi 2016-10-01 362
f75fdf22b0a8470 Miklos Szeredi 2016-10-01 363 return dentry->d_fsdata ? 0 : -ENOMEM;
f75fdf22b0a8470 Miklos Szeredi 2016-10-01 364 }
f75fdf22b0a8470 Miklos Szeredi 2016-10-01 @365 static void fuse_dentry_release(struct dentry *dentry)
f75fdf22b0a8470 Miklos Szeredi 2016-10-01 366 {
be926e6761d28d1 Paul Lawrence 2021-12-02 367 struct fuse_dentry *fd = dentry->d_fsdata;
be926e6761d28d1 Paul Lawrence 2021-12-02 368
:::::: The code at line 365 was first introduced by commit
:::::: f75fdf22b0a84702d1b72fc1ccd53dcdde121c16 fuse: don't use ->d_time
:::::: TO: Miklos Szeredi <mszeredi@redhat.com>
:::::: CC: Miklos Szeredi <mszeredi@redhat.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-21 13:49 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=202607212136.NJMMrW69-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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 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.