From: "Darrick J. Wong" <djwong@kernel.org>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: [PATCHSET 2/6] fuse2fs: refactor unmount code
Date: Mon, 15 Sep 2025 16:58:50 -0700 [thread overview]
Message-ID: <175798064383.349669.5686318690824770898.stgit@frogsfrogsfrogs> (raw)
Hi all,
In this series, we refactor the code around ext2fs_close to get ready
for iomap mode. The significant part of this series is moving the
unmount code to op_destroy, because we want to release the block device
as a part of the umount(2) process to maintain expected behavior of the
in-kernel local filesystem drivers.
If you're going to start using this code, I strongly recommend pulling
from my git trees, which are linked below.
Comments and questions are, as always, welcome.
e2fsprogs git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/e2fsprogs.git/log/?h=fuse2fs-refactor-unmounting
---
Commits in this patchset:
* fuse2fs: get rid of the global_fs variable
* fuse2fs: hoist lockfile code
* fuse2fs: hoist unmount code from main
---
misc/fuse2fs.c | 189 +++++++++++++++++++++++++++++++-------------------------
1 file changed, 104 insertions(+), 85 deletions(-)
next reply other threads:[~2025-09-15 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 23:58 Darrick J. Wong [this message]
2025-09-16 0:01 ` [PATCH 1/3] fuse2fs: get rid of the global_fs variable Darrick J. Wong
2025-09-16 0:01 ` [PATCH 2/3] fuse2fs: hoist lockfile code Darrick J. Wong
2025-09-16 0:02 ` [PATCH 3/3] fuse2fs: hoist unmount code from main Darrick J. Wong
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=175798064383.349669.5686318690824770898.stgit@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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