[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250523140344.GA1414791@mit.edu>
Date: Fri, 23 May 2025 10:03:44 -0400
From: "Theodore Ts'o" <tytso@....edu>
To: "Darrick J. Wong" <djwong@...nel.org>
Cc: linux-ext4@...r.kernel.org
Subject: Re: [PATCHSET 1/6] fuse2fs: even more bug fixes
On Wed, May 21, 2025 at 03:34:36PM -0700, Darrick J. Wong wrote:
> Hi all,
>
> This series fixes even more bugs in fuse2fs.
Thanks, applied. I found that it didn't compile, because it used
fuse2fs_{read,write}_inode() which doesn't get defined until PATCHSET
2/6. So I've also applied the second patchset, and then split the
patch "fuse2fs: simplify reading and writing inodes" into two commits,
and applied the first half before "fuse2fs: fix removing ea inodes when
freeing a file" to keep the fuse2fs changes bisectable.
Also, I cleaned up some patches to keep fuse2fs portable enough to
work with MacOS. I've lightly tested fuse2fs with MacFuse (installed
via MacPorts) on macOS Sequoia and it works without having to pay $$$
to Apple. You do need to enable the MacFuse system extension (which
is signed by Benjamin Fleischer, so I guess Fleischer is the one who
paid $3000 to Apple) and reboot, but it does work.
I'll reach out to someone in FreeBSD land to test whether fuse2fs
works there, since I'd like to maintain cross-OS portability as much
as possible. It does mean that I'm a bit concerned about the fuseblk
patchset because I'm pretty sure that's Linux-specific, correct?
Cheers,
- Ted
Powered by blists - more mailing lists