diff options
author | 2025-02-27 12:33:26 +0100 | |
---|---|---|
committer | 2025-03-05 11:52:50 +0100 | |
commit | 21432f9b5eda2f531dc029d8422280106834d5f7 (patch) | |
tree | a3b7bfc30caa76f4c92d92ef270cc5baa2536209 /mm/util.c | |
parent | Merge patch series "prep patches for my mkdir series" (diff) | |
parent | VFS: Change vfs_mkdir() to return the dentry. (diff) | |
download | wireguard-linux-21432f9b5eda2f531dc029d8422280106834d5f7.tar.xz wireguard-linux-21432f9b5eda2f531dc029d8422280106834d5f7.zip |
Merge patch series "Change inode_operations.mkdir to return struct dentry *"
NeilBrown <neilb@suse.de> says:
This revised series contains a few clean-ups as requested by various
people but no substantial changes.
I reviewed the mkdir functions in many (all?) filesystems and found a
few that use d_instantiate() on an unlocked inode (after
unlock_new_inode()) and also support export_operations. These could
potentially call d_instantiate() on a directory inode which is already
attached to a dentry, though making that happen would usually require
guessing the filehandle correctly. I haven't tried to address those
here, (this patch set doesn't make that situation any worse) but I may
in the future.
* patches from https://lore.kernel.org/r/20250227013949.536172-2-neilb@suse.de:
VFS: Change vfs_mkdir() to return the dentry.
nfs: change mkdir inode_operation to return alternate dentry if needed.
fuse: return correct dentry for ->mkdir
ceph: return the correct dentry on mkdir
hostfs: store inode in dentry after mkdir if possible.
Change inode_operations.mkdir to return struct dentry *
Link: https://lore.kernel.org/r/20250227013949.536172-2-neilb@suse.de
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'mm/util.c')
0 files changed, 0 insertions, 0 deletions