From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Amir Goldstein <amir73il@gmail.com>
Subject: fs/bpf_fs_kfuncs.c:377:26: sparse: sparse: symbol 'bpf_real_data_inode' was not declared. Should it be static?
Date: Wed, 12 Aug 2026 16:29:53 +0800 [thread overview]
Message-ID: <202608121600.AhWHKX74-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: d58772d8520c7ef247c4b95c9bd76d3a25da9ff5
commit: 3f8c65b06fafc3f779abda5f7b81707411d05d4c bpf: have bpf_real_data_inode() take a struct file
date: 6 weeks ago
config: mips-randconfig-r134-20260812 (https://download.01.org/0day-ci/archive/20260812/202608121600.AhWHKX74-lkp@intel.com/config)
compiler: clang version 24.0.0git (https://github.com/llvm/llvm-project 12df34b8469b8095359de8c249cb1b2753fadeea)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260812/202608121600.AhWHKX74-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: 3f8c65b06faf ("bpf: have bpf_real_data_inode() take a struct file")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608121600.AhWHKX74-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/bpf_fs_kfuncs.c:377:26: sparse: sparse: symbol 'bpf_real_data_inode' was not declared. Should it be static?
vim +/bpf_real_data_inode +377 fs/bpf_fs_kfuncs.c
361
362 /**
363 * bpf_real_data_inode - get the real inode hosting a file's data
364 * @file: file to resolve
365 *
366 * Resolve @file to the inode that hosts its data. For a regular file on a
367 * union/overlay filesystem this is the underlying (upper or lower) inode that
368 * stores the data, not the overlay inode.
369 *
370 * Data resolution only applies to regular files. For a non-regular file (e.g.
371 * a device node, fifo or socket) on a union/overlay filesystem the overlay
372 * inode itself is returned; for any file on a non-union filesystem the inode
373 * attached to @file is returned.
374 *
375 * Return: The inode hosting @file's data, or NULL.
376 */
> 377 __bpf_kfunc struct inode *bpf_real_data_inode(struct file *file)
378 {
379 return d_real_inode(file_dentry(file));
380 }
381
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-12 8:30 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=202608121600.AhWHKX74-lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.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 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.