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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <aQHf3UGaURFzC17U@infradead.org>
Date: Wed, 29 Oct 2025 02:35:25 -0700
From: Christoph Hellwig <hch@...radead.org>
To: "Darrick J. Wong" <djwong@...nel.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

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.