Re: [PATCH] docs: add guidelines for submitting new filesystems

[Matthew Wilcox <willy@infradead.org>]

On Fri, Apr 17, 2026 at 04:25:03PM +0200, Amir Goldstein wrote:
> +Be testable
> +  The filesystem must be testable in a meaningful way.  The
> +  `fstests <https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git>`_
> +  framework (also known as xfstests) is the standard testing infrastructure
> +  for Linux filesystems and its use is highly recommended.  At a minimum,
> +  there must be a credible and documented way to test the filesystem and
> +  detect regressions.  When submitting, include a summary of test results
> +  indicating which tests pass, fail, or are not applicable.

Perhaps we need a section on fuzzing?  Maybe something like this:

Fuzzing
  Filesystems in the Linux kernel are subjected to various fuzzing
  activities, by academic researchers, syzbot and malicious actors.
  Your filesystem will need to be robust against not just random
  syscalls but also fuzzed (corrupted) filesystem images (for block
  based filesystems) and crafted hostile network messages (for network
  filesystems).  It should react appropriately to such attacks,
  by repairing or reporting a corrupted filesystem, but not hanging
  executing BUG() or WARN() statements or otherwise corrupting the kernel.

Happy for you to reword that.