linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: linux-fsdevel@vger.kernel.org
Cc: Alexander Viro <viro@zeniv.linux.org.uk>, Jan Kara <jack@suse.cz>,
	 linux-btrfs@vger.kernel.org, linux-ext4@vger.kernel.org,
	 linux-xfs@vger.kernel.org,
	Christian Brauner <brauner@kernel.org>
Subject: [PATCH RFC 0/8] fs: introduce super write guard
Date: Tue, 04 Nov 2025 13:12:29 +0100	[thread overview]
Message-ID: <20251104-work-guards-v1-0-5108ac78a171@kernel.org> (raw)

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@kernel.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


             reply	other threads:[~2025-11-04 12:12 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 12:12 Christian Brauner [this message]
2025-11-04 12:12 ` [PATCH RFC 1/8] fs: add super_write_guard Christian Brauner
2025-11-04 12:32   ` Jan Kara
2025-11-04 12:12 ` [PATCH RFC 2/8] btrfs: use super write guard in btrfs_reclaim_bgs_work() Christian Brauner
2025-11-04 20:42   ` Qu Wenruo
2025-11-05 16:33     ` Daniel Vacek
2025-11-04 12:12 ` [PATCH RFC 3/8] btrfs: use super write guard btrfs_run_defrag_inode() Christian Brauner
2025-11-05 16:38   ` Daniel Vacek
2025-11-06  8:19   ` David Sterba
2025-11-04 12:12 ` [PATCH RFC 4/8] btrfs: use super write guard in sb_start_write() Christian Brauner
2025-11-04 17:00   ` Mateusz Guzik
2025-11-04 20:56     ` Christian Brauner
2025-11-04 12:12 ` [PATCH RFC 5/8] ext4: use super write guard in write_mmp_block() Christian Brauner
2025-11-04 12:32   ` Jan Kara
2025-11-04 13:06   ` Theodore Ts'o
2025-11-05 18:33   ` Daniel Vacek
2025-11-06  9:24     ` Jan Kara
2025-11-06 10:04       ` Daniel Vacek
2025-11-04 12:12 ` [PATCH RFC 6/8] btrfs: use super write guard in relocating_repair_kthread() Christian Brauner
2025-11-04 12:12 ` [PATCH RFC 7/8] open: use super write guard in do_ftruncate() Christian Brauner
2025-11-04 12:32   ` Jan Kara
2025-11-05 18:37   ` Daniel Vacek
2025-11-04 12:12 ` [PATCH RFC 8/8] xfs: use super write guard in xfs_file_ioctl() Christian Brauner
2025-11-04 17:08   ` Darrick J. Wong
2025-11-04 20:57     ` Christian Brauner
2025-11-05 17:47       ` Darrick J. Wong
2025-11-05 18:40   ` Daniel Vacek

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=20251104-work-guards-v1-0-5108ac78a171@kernel.org \
    --to=brauner@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).