All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Christian Brauner <christianvanbrauner@gmail.com>
Subject: [brauner-vfs:vfs.all 356/378] fs/nullfs.c:55:14: error: use of undeclared identifier 'nullfs_nolease'; did you mean 'nullfs_nolock'?
Date: Mon, 05 Oct 2026 02:57:10 +0200	[thread overview]
Message-ID: <202610050233.4otV9Kjb-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git vfs.all
head:   4852668f27dd07a38b753c3ad673ffb0bc3c00ec
commit: 580de1b24ab7a3e0cb73db6c341bf40d7f683797 [356/378] nullfs: add an empty immutable regular file
config: i386-randconfig-r2307-20261004 (https://download.01.org/0day-ci/archive/20261005/202610050233.4otV9Kjb-lkp@intel.com/config)
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261005/202610050233.4otV9Kjb-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/202610050233.4otV9Kjb-lkp@intel.com/

All errors (new ones prefixed by >>):

>> fs/nullfs.c:55:14: error: use of undeclared identifier 'nullfs_nolease'; did you mean 'nullfs_nolock'?
      55 |         .setlease       = nullfs_nolease,
         |                           ^~~~~~~~~~~~~~
         |                           nullfs_nolock
   fs/nullfs.c:26:12: note: 'nullfs_nolock' declared here
      26 | static int nullfs_nolock(struct file *file, int cmd, struct file_lock *fl)
         |            ^
>> fs/nullfs.c:55:14: error: incompatible function pointer types initializing 'int (*)(struct file *, int, struct file_lease **, void **)' with an expression of type 'int (struct file *, int, struct file_lock *)' [-Wincompatible-function-pointer-types]
      55 |         .setlease       = nullfs_nolease,
         |                           ^~~~~~~~~~~~~~
   2 errors generated.


vim +55 fs/nullfs.c

    47	
    48	/* an empty regular file, with the same refusals as the directory */
    49	static const struct file_operations nullfs_file_operations = {
    50		.llseek		= generic_file_llseek,
    51		.read_iter	= nullfs_file_read_iter,
    52		.fsync		= noop_fsync,
    53		.lock		= nullfs_nolock,
    54		.flock		= nullfs_nolock,
  > 55		.setlease	= nullfs_nolease,
    56	};
    57	

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

                 reply	other threads:[~2026-10-05  0:58 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=202610050233.4otV9Kjb-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=brauner@kernel.org \
    --cc=christianvanbrauner@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 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.