Linux EXT4 FS development
 help / color / mirror / Atom feed
* [PATCHSET 2/6] fuse2fs: refactor unmount code
@ 2025-09-15 23:58 Darrick J. Wong
  2025-09-16  0:01 ` [PATCH 1/3] fuse2fs: get rid of the global_fs variable Darrick J. Wong
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: Darrick J. Wong @ 2025-09-15 23:58 UTC (permalink / raw)
  To: tytso; +Cc: linux-ext4

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(-)


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2025-09-16  0:02 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-09-15 23:58 [PATCHSET 2/6] fuse2fs: refactor unmount code Darrick J. Wong
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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox