From: "Darrick J. Wong" <djwong@kernel.org>
To: tytso@mit.edu
Cc: linux-ext4@vger.kernel.org
Subject: [PATCHSET 3/6] fuse2fs: refactor mount code
Date: Mon, 15 Sep 2025 16:58:55 -0700 [thread overview]
Message-ID: <175798064569.349841.5710112269701643406.stgit@frogsfrogsfrogs> (raw)
Hi all,
Here, we hoist the mounting code out of main() into a pile of separate
helper functions to reduce the complexity of understanding the mount
code. This isn't required for iomap, but it is necessary for the
fuseblk mode introduced in the next series.
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-mounting
---
Commits in this patchset:
* fuse2fs: split filesystem mounting into helper functions
* fuse2fs: make norecovery behavior consistent with the kernel
* fuse2fs: recheck support after replaying journal
---
misc/fuse2fs.c | 312 ++++++++++++++++++++++++++++++++++----------------------
1 file changed, 187 insertions(+), 125 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:02 ` [PATCH 1/3] fuse2fs: split filesystem mounting into helper functions Darrick J. Wong
2025-09-16 0:02 ` [PATCH 2/3] fuse2fs: make norecovery behavior consistent with the kernel Darrick J. Wong
2025-09-16 0:02 ` [PATCH 3/3] fuse2fs: recheck support after replaying journal 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=175798064569.349841.5710112269701643406.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