From: Al Viro <viro@zeniv.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-fsdevel@vger.kernel.org, Christian Brauner <brauner@kernel.org>
Subject: [git pull][6.17] vfs.git 2/9: simple_recursive_removal
Date: Sat, 26 Jul 2025 09:02:24 +0100 [thread overview]
Message-ID: <20250726080224.GA1456602@ZenIV> (raw)
In-Reply-To: <20250726080119.GA222315@ZenIV>
The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:
Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git tags/pull-simple_recursive_removal
for you to fetch changes up to bad356bb50e64170f8af14a00797a04313846aeb:
functionfs, gadgetfs: use simple_recursive_removal() (2025-07-02 22:36:52 -0400)
----------------------------------------------------------------
Removing subtrees of kernel filesystems is done in quite a few
places; unfortunately, it's easy to get wrong. A number of open-coded
attempts are out there, with varying amount of bogosities.
simple_recursive_removal() had been introduced for doing that with
all precautions needed; it does an equivalent of rm -rf, with sufficient
locking, eviction of anything mounted on top of the subtree, etc.
This series converts a bunch of open-coded instances to using that.
----------------------------------------------------------------
Al Viro (9):
simple_recursive_removal(): saner interaction with fsnotify
better lockdep annotations for simple_recursive_removal()
add locked_recursive_removal()
spufs: switch to locked_recursive_removal()
binfmt_misc: switch to locked_recursive_removal()
pstore: switch to locked_recursive_removal()
fuse_ctl: use simple_recursive_removal()
kill binderfs_remove_file()
functionfs, gadgetfs: use simple_recursive_removal()
arch/powerpc/platforms/cell/spufs/inode.c | 49 ++++++-------------------------
drivers/android/binder.c | 2 +-
drivers/android/binder_internal.h | 2 --
drivers/android/binderfs.c | 15 ----------
drivers/usb/gadget/function/f_fs.c | 3 +-
drivers/usb/gadget/legacy/inode.c | 7 +----
fs/binfmt_misc.c | 44 ++-------------------------
fs/fuse/control.c | 30 ++++++++-----------
fs/fuse/fuse_i.h | 6 ----
fs/libfs.c | 32 ++++++++++++++------
fs/pstore/inode.c | 5 ++--
include/linux/fs.h | 2 ++
12 files changed, 55 insertions(+), 142 deletions(-)
next prev parent reply other threads:[~2025-07-26 8:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-26 8:01 [git pull][6.17] vfs.git 1/9: d_flags pile Al Viro
2025-07-26 8:02 ` Al Viro [this message]
2025-07-28 23:41 ` [git pull][6.17] vfs.git 2/9: simple_recursive_removal pr-tracker-bot
2025-07-26 8:03 ` [git pull][6.17] vfs.git 3/9: rpc_pipefs Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:04 ` [git pull][6.17] vfs.git 4/9: asm/param.h pile Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:05 ` [git pull][6.17] vfs.git 5/9: securityfs Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:05 ` [git pull][6.17] vfs.git 6/9: misc pile Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:08 ` [git pull][6.17] vfs.git 7/9: ceph d_name fixes Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:08 ` [git pull][6.17] vfs.git 8/9: CLASS(fd) followup Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-26 8:09 ` [git pull][6.17] vfs.git 9/9: mount pile Al Viro
2025-07-28 23:41 ` pr-tracker-bot
2025-07-28 23:41 ` [git pull][6.17] vfs.git 1/9: d_flags pile pr-tracker-bot
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=20250726080224.GA1456602@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).