All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jlayton:dir-deleg 20/42] fs/namei.c:3492:31: error: 'LEASE_BREAK_DIR_CREATE' undeclared; did you mean 'FL_IGN_DIR_CREATE'?
Date: Wed, 5 Nov 2025 15:28:36 +0800	[thread overview]
Message-ID: <202511051517.RT1fpMJM-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git dir-deleg
head:   c4fcd7f276a417ffe8f80480c5c929b6764602d2
commit: 7e793d3d38f1b5bc5ac94a95dc4138ec1baa9db0 [20/42] filelock: add support for ignoring deleg breaks for dir change events
config: arc-randconfig-001-20251105 (https://download.01.org/0day-ci/archive/20251105/202511051517.RT1fpMJM-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251105/202511051517.RT1fpMJM-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/202511051517.RT1fpMJM-lkp@intel.com/

All errors (new ones prefixed by >>):

   fs/namei.c: In function 'vfs_create':
>> fs/namei.c:3492:31: error: 'LEASE_BREAK_DIR_CREATE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_CREATE'?
     error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, args->delegated_inode);
                                  ^~~~~~~~~~~~~~~~~~~~~~
                                  FL_IGN_DIR_CREATE
   fs/namei.c:3492:31: note: each undeclared identifier is reported only once for each function it appears in
   fs/namei.c: In function 'lookup_open':
   fs/namei.c:3792:38: error: 'LEASE_BREAK_DIR_CREATE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_CREATE'?
      error = try_break_deleg(dir_inode, LEASE_BREAK_DIR_CREATE, delegated_inode);
                                         ^~~~~~~~~~~~~~~~~~~~~~
                                         FL_IGN_DIR_CREATE
   fs/namei.c: In function 'vfs_mknod':
   fs/namei.c:4341:31: error: 'LEASE_BREAK_DIR_CREATE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_CREATE'?
     error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
                                  ^~~~~~~~~~~~~~~~~~~~~~
                                  FL_IGN_DIR_CREATE
   fs/namei.c: In function 'vfs_mkdir':
   fs/namei.c:4492:31: error: 'LEASE_BREAK_DIR_CREATE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_CREATE'?
     error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
                                  ^~~~~~~~~~~~~~~~~~~~~~
                                  FL_IGN_DIR_CREATE
   fs/namei.c: In function 'vfs_rmdir':
>> fs/namei.c:4598:31: error: 'LEASE_BREAK_DIR_DELETE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_DELETE'?
     error = try_break_deleg(dir, LEASE_BREAK_DIR_DELETE, delegated_inode);
                                  ^~~~~~~~~~~~~~~~~~~~~~
                                  FL_IGN_DIR_DELETE
   fs/namei.c: In function 'vfs_unlink':
   fs/namei.c:4731:33: error: 'LEASE_BREAK_DIR_DELETE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_DELETE'?
       error = try_break_deleg(dir, LEASE_BREAK_DIR_DELETE, delegated_inode);
                                    ^~~~~~~~~~~~~~~~~~~~~~
                                    FL_IGN_DIR_DELETE
   fs/namei.c: In function 'vfs_symlink':
   fs/namei.c:4883:31: error: 'LEASE_BREAK_DIR_CREATE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_CREATE'?
     error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
                                  ^~~~~~~~~~~~~~~~~~~~~~
                                  FL_IGN_DIR_CREATE
   fs/namei.c: In function 'vfs_link':
   fs/namei.c:5015:32: error: 'LEASE_BREAK_DIR_CREATE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_CREATE'?
      error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
                                   ^~~~~~~~~~~~~~~~~~~~~~
                                   FL_IGN_DIR_CREATE
   fs/namei.c: In function 'vfs_rename':
>> fs/namei.c:5285:26: error: 'LEASE_BREAK_DIR_RENAME' undeclared (first use in this function); did you mean 'FL_IGN_DIR_RENAME'?
        old_dir == new_dir ? LEASE_BREAK_DIR_RENAME :
                             ^~~~~~~~~~~~~~~~~~~~~~
                             FL_IGN_DIR_RENAME
   fs/namei.c:5286:12: error: 'LEASE_BREAK_DIR_DELETE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_DELETE'?
               LEASE_BREAK_DIR_DELETE,
               ^~~~~~~~~~~~~~~~~~~~~~
               FL_IGN_DIR_DELETE
   fs/namei.c:5291:36: error: 'LEASE_BREAK_DIR_CREATE' undeclared (first use in this function); did you mean 'FL_IGN_DIR_CREATE'?
      error = try_break_deleg(new_dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
                                       ^~~~~~~~~~~~~~~~~~~~~~
                                       FL_IGN_DIR_CREATE


vim +3492 fs/namei.c

  3460	
  3461	/**
  3462	 * vfs_create - create new file
  3463	 * @args:	struct createdata describing create to be done
  3464	 *
  3465	 * Create a new file.
  3466	 *
  3467	 * If the inode has been found through an idmapped mount the idmap of
  3468	 * the vfsmount must be passed through @args->idmap. This function will then take
  3469	 * care to map the inode according to @args->idmap before checking permissions.
  3470	 * On non-idmapped mounts or if permission checking is to be performed on the
  3471	 * raw inode simply pass @nop_mnt_idmap.
  3472	 */
  3473	int vfs_create(struct createdata *args)
  3474	{
  3475		struct mnt_idmap *idmap = args->idmap;
  3476		struct inode *dir = args->dir;
  3477		struct dentry *dentry = args->dentry;
  3478		umode_t mode = args->mode;
  3479		int error;
  3480	
  3481		error = may_create(idmap, dir, dentry);
  3482		if (error)
  3483			return error;
  3484	
  3485		if (!dir->i_op->create)
  3486			return -EACCES;	/* shouldn't it be ENOSYS? */
  3487	
  3488		mode = vfs_prepare_mode(idmap, dir, mode, S_IALLUGO, S_IFREG);
  3489		error = security_inode_create(dir, dentry, mode);
  3490		if (error)
  3491			return error;
> 3492		error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, args->delegated_inode);
  3493		if (error)
  3494			return error;
  3495		error = dir->i_op->create(idmap, dir, dentry, mode, true);
  3496		if (!error)
  3497			fsnotify_create(dir, dentry);
  3498		return error;
  3499	}
  3500	EXPORT_SYMBOL(vfs_create);
  3501	

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

                 reply	other threads:[~2025-11-05  7:29 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=202511051517.RT1fpMJM-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jlayton@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.