From: kernel test robot <lkp@intel.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [jlayton:kdevops 4/26] fs/namei.c:4173:31: error: use of undeclared identifier 'LEASE_BREAK_DIR_CREATE'
Date: Thu, 26 Mar 2026 12:02:13 +0800 [thread overview]
Message-ID: <202603261133.R0SpGbfl-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jlayton/linux.git kdevops
head: 996759a25534ab4a7e986fe0153659e93c1611ec
commit: e7730a146d19c905b78c9c16be3d172b194ab963 [4/26] filelock: add support for ignoring deleg breaks for dir change events
config: i386-buildonly-randconfig-004-20260326 (https://download.01.org/0day-ci/archive/20260326/202603261133.R0SpGbfl-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260326/202603261133.R0SpGbfl-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/202603261133.R0SpGbfl-lkp@intel.com/
All errors (new ones prefixed by >>):
>> fs/namei.c:4173:31: error: use of undeclared identifier 'LEASE_BREAK_DIR_CREATE'
4173 | error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, di);
| ^
fs/namei.c:4472:38: error: use of undeclared identifier 'LEASE_BREAK_DIR_CREATE'
4472 | error = try_break_deleg(dir_inode, LEASE_BREAK_DIR_CREATE, delegated_inode);
| ^
fs/namei.c:5088:31: error: use of undeclared identifier 'LEASE_BREAK_DIR_CREATE'
5088 | error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
| ^
fs/namei.c:5229:31: error: use of undeclared identifier 'LEASE_BREAK_DIR_CREATE'
5229 | error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
| ^
>> fs/namei.c:5334:31: error: use of undeclared identifier 'LEASE_BREAK_DIR_DELETE'
5334 | error = try_break_deleg(dir, LEASE_BREAK_DIR_DELETE, delegated_inode);
| ^
fs/namei.c:5464:33: error: use of undeclared identifier 'LEASE_BREAK_DIR_DELETE'
5464 | error = try_break_deleg(dir, LEASE_BREAK_DIR_DELETE, delegated_inode);
| ^
fs/namei.c:5611:31: error: use of undeclared identifier 'LEASE_BREAK_DIR_CREATE'
5611 | error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
| ^
fs/namei.c:5742:32: error: use of undeclared identifier 'LEASE_BREAK_DIR_CREATE'
5742 | error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
| ^
>> fs/namei.c:6009:26: error: use of undeclared identifier 'LEASE_BREAK_DIR_RENAME'
6009 | old_dir == new_dir ? LEASE_BREAK_DIR_RENAME :
| ^
fs/namei.c:6010:12: error: use of undeclared identifier 'LEASE_BREAK_DIR_DELETE'
6010 | LEASE_BREAK_DIR_DELETE,
| ^
fs/namei.c:6015:36: error: use of undeclared identifier 'LEASE_BREAK_DIR_CREATE'
6015 | error = try_break_deleg(new_dir, LEASE_BREAK_DIR_CREATE, delegated_inode);
| ^
11 errors generated.
vim +/LEASE_BREAK_DIR_CREATE +4173 fs/namei.c
4140
4141 /**
4142 * vfs_create - create new file
4143 * @idmap: idmap of the mount the inode was found from
4144 * @dentry: dentry of the child file
4145 * @mode: mode of the child file
4146 * @di: returns parent inode, if the inode is delegated.
4147 *
4148 * Create a new file.
4149 *
4150 * If the inode has been found through an idmapped mount the idmap of
4151 * the vfsmount must be passed through @idmap. This function will then take
4152 * care to map the inode according to @idmap before checking permissions.
4153 * On non-idmapped mounts or if permission checking is to be performed on the
4154 * raw inode simply pass @nop_mnt_idmap.
4155 */
4156 int vfs_create(struct mnt_idmap *idmap, struct dentry *dentry, umode_t mode,
4157 struct delegated_inode *di)
4158 {
4159 struct inode *dir = d_inode(dentry->d_parent);
4160 int error;
4161
4162 error = may_create_dentry(idmap, dir, dentry);
4163 if (error)
4164 return error;
4165
4166 if (!dir->i_op->create)
4167 return -EACCES; /* shouldn't it be ENOSYS? */
4168
4169 mode = vfs_prepare_mode(idmap, dir, mode, S_IALLUGO, S_IFREG);
4170 error = security_inode_create(dir, dentry, mode);
4171 if (error)
4172 return error;
> 4173 error = try_break_deleg(dir, LEASE_BREAK_DIR_CREATE, di);
4174 if (error)
4175 return error;
4176 error = dir->i_op->create(idmap, dir, dentry, mode, true);
4177 if (!error)
4178 fsnotify_create(dir, dentry);
4179 return error;
4180 }
4181 EXPORT_SYMBOL(vfs_create);
4182
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-03-26 4:03 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=202603261133.R0SpGbfl-lkp@intel.com \
--to=lkp@intel.com \
--cc=jlayton@kernel.org \
--cc=llvm@lists.linux.dev \
--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.