linux-ext4 - Re: [PATCHSET v6] fstests: support ext4 fuse testing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20251029235234.GZ6178@frogsfrogsfrogs>
Date: Wed, 29 Oct 2025 16:52:34 -0700
From: "Darrick J. Wong" <djwong@...nel.org>
To: Christoph Hellwig <hch@...radead.org>
Cc: zlang@...hat.com, fstests@...r.kernel.org, neal@...pa.dev,
	linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	joannelkoong@...il.com, bernd@...ernd.com
Subject: Re: [PATCHSET v6] fstests: support ext4 fuse testing

On Wed, Oct 29, 2025 at 02:35:25AM -0700, Christoph Hellwig wrote:
> I find the series a bit hard to follow, because it mixes generic
> with fs specific with test specific patches totally randomly.  Can
> you get a bit of an order into it?  And maybe just send a series
> with the conceptual core changes first outside the giant patch bombs?
> Or if parts are useful outside the fuse ext4 context just send them
> out in a self-contained series?  Bonus points for a bit of a highlevel
> summary why these changes are needed in the cover letter.

Well TBH there's a lot of accumulated stuff including some treewide
cleanups in my fstests branch that needs to go upstream before the
fuse2fs changes.  I've been waiting the entire year to see if
check-parallel will get finished... and I'm not going to wait anymore.
That's why I haven't tidied up this patchset at all.

The TLDR version is that FSTYP=fuse.ext4 is how you select the fuse
server, and you ought to have mkfs.fuse.ext4/fsck.fuse.ext4 point to the
appropriate e2fsprogs programs; a [fuse.ext4] section in mke2fs.conf;
and fuse4fs installed as /sbin/mount.fuse.ext4 or /sbin/ext4 depending
on how your libfuse is configured.

Then this series is basically making sure that FSTYP=fuse.ext* works,
and turning off feature tests for things that aren't supported by
fuse2fs.

--D