From: Linus Torvalds <torvalds@linux-foundation.org>
Date: Mon, 13 Apr 2026 17:24:33 +0000 (-0700)
Subject: Merge tag 'vfs-7.1-rc1.directory' of git://git.kernel.org/pub/scm/linux/kernel/git... 
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=3383589700ea1c196f05b164d2b6c15269b6e9e4;p=thirdparty%2Fkernel%2Flinux.git

Merge tag 'vfs-7.1-rc1.directory' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs

Pull vfs directory updates from Christian Brauner:
 "Recently 'start_creating', 'start_removing', 'start_renaming' and
  related interfaces were added which combine the locking and the
  lookup.

  At that time many callers were changed to use the new interfaces.
  However there are still an assortment of places out side of the core
  vfs where the directory is locked explictly, whether with inode_lock()
  or lock_rename() or similar. These were missed in the first pass for
  an assortment of uninteresting reasons.

  This addresses the remaining places where explicit locking is used,
  and changes them to use the new interfaces, or otherwise removes the
  explicit locking.

  The biggest changes are in overlayfs. The other changes are quite
  simple, though maybe the cachefiles changes is the least simple of
  those"

* tag 'vfs-7.1-rc1.directory' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs:
  VFS: unexport lock_rename(), lock_rename_child(), unlock_rename()
  ovl: remove ovl_lock_rename_workdir()
  ovl: use is_subdir() for testing if one thing is a subdir of another
  ovl: change ovl_create_real() to get a new lock when re-opening created file.
  ovl: pass name buffer to ovl_start_creating_temp()
  cachefiles: change cachefiles_bury_object to use start_renaming_dentry()
  ovl: Simplify ovl_lookup_real_one()
  VFS: make lookup_one_qstr_excl() static.
  nfsd: switch purge_old() to use start_removing_noperm()
  selinux: Use simple_start_creating() / simple_done_creating()
  Apparmor: Use simple_start_creating() / simple_done_creating()
  libfs: change simple_done_creating() to use end_creating()
  VFS: move the start_dirop() kerndoc comment to before start_dirop()
  fs/proc: Don't lock root inode when creating "self" and "thread-self"
  VFS: note error returns in documentation for various lookup functions
---

3383589700ea1c196f05b164d2b6c15269b6e9e4
diff --cc security/apparmor/apparmorfs.c
index 242c71b3fb6ef,f93c4f31d02ae..ac0ffcb03c023
--- a/security/apparmor/apparmorfs.c
+++ b/security/apparmor/apparmorfs.c
@@@ -364,22 -289,13 +358,17 @@@ static struct dentry *aafs_create(cons
  	}
  
  	error = __aafs_setup_d_inode(dir, dentry, mode, data, link, fops, iops);
+ 	simple_done_creating(dentry);
  	if (error)
- 		goto fail_dentry;
- 	inode_unlock(dir);
+ 		goto fail;
 +
 +	if (data)
 +		aa_get_common_ref(data);
 +
  	return dentry;
  
- fail_dentry:
- 	dput(dentry);
- 
- fail_lock:
- 	inode_unlock(dir);
+ fail:
  	simple_release_fs(&aafs_mnt, &aafs_count);
- 
  	return ERR_PTR(error);
  }