[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251104-work-guards-v1-0-5108ac78a171@kernel.org>
Date: Tue, 04 Nov 2025 13:12:29 +0100
From: Christian Brauner <brauner@...nel.org>
To: linux-fsdevel@...r.kernel.org
Cc: Alexander Viro <viro@...iv.linux.org.uk>, Jan Kara <jack@...e.cz>,
linux-btrfs@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-xfs@...r.kernel.org, Christian Brauner <brauner@...nel.org>
Subject: [PATCH RFC 0/8] fs: introduce super write guard
Hey,
I'm in the process of adding a few more guards for vfs constructs.
I've chosen the easy case of super_start_write() and super_end_write()
and converted eligible callers. I think long-term we can move a lot of
the manual placement to completely rely on guards - where sensible.
Christian
Signed-off-by: Christian Brauner <brauner@...nel.org>
---
Christian Brauner (8):
fs: add super_write_guard
btrfs: use super write guard in btrfs_reclaim_bgs_work()
btrfs: use super write guard btrfs_run_defrag_inode()
btrfs: use super write guard in sb_start_write()
ext4: use super write guard in write_mmp_block()
btrfs: use super write guard in relocating_repair_kthread()
open: use super write guard in do_ftruncate()
xfs: use super write guard in xfs_file_ioctl()
fs/btrfs/block-group.c | 3 +--
fs/btrfs/defrag.c | 7 +++----
fs/btrfs/volumes.c | 7 ++++---
fs/ext4/mmp.c | 8 ++------
fs/open.c | 9 +++------
fs/xfs/xfs_ioctl.c | 6 ++----
include/linux/fs.h | 5 +++++
7 files changed, 20 insertions(+), 25 deletions(-)
---
base-commit: dcb6fa37fd7bc9c3d2b066329b0d27dedf8becaa
change-id: 20251104-work-guards-fe3d7a09e258
Powered by blists - more mailing lists