From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, brauner@kernel.org,
viro@zeniv.linux.org.uk, dsterba@suse.com,
Filipe Manana <fdmanana@suse.com>
Subject: [PATCH v2 0/4] btrfs: stop duplicating VFS code for subvolume/snapshot dentry
Date: Tue, 13 Jan 2026 12:39:49 +0000 [thread overview]
Message-ID: <cover.1768307858.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Currently btrfs has copies of two unexported functions from fs/namei.c
used in the snapshot/subvolume creation and deletion. This patchset
exports those functions and makes btrfs use them, to avoid duplication
and the burden of keeping the copies up to date.
V2: Updated changelog of patch 4/4 to mention the btrfs copy misses a
call to audit_inode_child().
Link to V1: https://lore.kernel.org/linux-btrfs/cover.1767801889.git.fdmanana@suse.com/
Filipe Manana (4):
fs: export may_delete() as may_delete_dentry()
fs: export may_create() as may_create_dentry()
btrfs: use may_delete_dentry() in btrfs_ioctl_snap_destroy()
btrfs: use may_create_dentry() in btrfs_mksubvol()
fs/btrfs/ioctl.c | 73 ++--------------------------------------------
fs/namei.c | 36 ++++++++++++-----------
include/linux/fs.h | 5 ++++
3 files changed, 26 insertions(+), 88 deletions(-)
--
2.47.2
next reply other threads:[~2026-01-13 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 12:39 fdmanana [this message]
2026-01-13 12:39 ` [PATCH v2 1/4] fs: export may_delete() as may_delete_dentry() fdmanana
2026-01-13 12:39 ` [PATCH v2 2/4] fs: export may_create() as may_create_dentry() fdmanana
2026-01-13 12:39 ` [PATCH v2 3/4] btrfs: use may_delete_dentry() in btrfs_ioctl_snap_destroy() fdmanana
2026-01-13 12:39 ` [PATCH v2 4/4] btrfs: use may_create_dentry() in btrfs_mksubvol() fdmanana
2026-01-13 21:24 ` [PATCH v2 0/4] btrfs: stop duplicating VFS code for subvolume/snapshot dentry David Sterba
2026-01-14 16:18 ` Christian Brauner
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=cover.1768307858.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--cc=brauner@kernel.org \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox