)]}'
{
  "log": [
    {
      "commit": "acb6d4cb84205a8e3f19ca470cfcf7bf6d93a509",
      "tree": "e561df373d23656e490ec462d1698bd5551b72d4",
      "parents": [
        "65caee6192ce5006bedbd40cc2889e0961c93b46"
      ],
      "author": {
        "name": "Disha Goel",
        "email": "disgoel@linux.ibm.com",
        "time": "Mon Jun 08 10:23:28 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Jun 17 19:34:26 2026"
      },
      "message": "common/defrag: skip defrag tests on DAX-enabled filesystems\n\nOnline defragmentation is not supported on ext4 DAX-enabled filesystems.\nThe ext4 defrag ioctl (EXT4_IOC_MOVE_EXT) returns EOPNOTSUPP when used\non DAX files.\n\nAdd an ext4-specific check in _require_defrag() to skip tests when DAX\nis enabled, avoiding false failures on ext4/301-304, ext4/308, and\ngeneric/018.\n\nXFS defrag works with DAX, so this check is ext4-specific.\n\nSuggested-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nReviewed-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "65caee6192ce5006bedbd40cc2889e0961c93b46",
      "tree": "ca3ccef30fd3b7678b5ec04f1828a356bbd3170d",
      "parents": [
        "26eb955e4243495c0df0bc2f157cda32edccf18b"
      ],
      "author": {
        "name": "Joanne Chang",
        "email": "joannechien@google.com",
        "time": "Tue Jun 02 07:19:11 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Jun 17 19:28:41 2026"
      },
      "message": "generic/63{4,5}: Modify criteria for passing test\n\nThe two tests pass when a timestamp is not preserved after the remount,\nbecause \"cmp -s\" does not print to the output file, and status is set to\n0 regardless of the return value of cmp. So, use \"diff\" instead to\ncorrectly fail the test and flag the error case in the output file.\n\nAlso, as the tests are focused on timestamps, don\u0027t print file contents\nso the tests can still pass if only the file contents differ.\n\nSigned-off-by: Joanne Chang \u003cjoannechien@google.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "26eb955e4243495c0df0bc2f157cda32edccf18b",
      "tree": "9cfc0df258b72aa69f498e4aacde42378a0bf926",
      "parents": [
        "88b140d74b3e01484db5c080165d5d7240d8ce0c"
      ],
      "author": {
        "name": "Christoph Hellwig",
        "email": "hch@lst.de",
        "time": "Wed Jun 17 06:04:17 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Jun 17 09:34:48 2026"
      },
      "message": "generic/366: check minimum dio size correctly\n\nmin_dio_alignment requires the file system to be checked to be mounted,\nso move the call into the main loop.  Drop the pointless blocksize\nargument to _require_odirect, which is only tested on the test device.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "88b140d74b3e01484db5c080165d5d7240d8ce0c",
      "tree": "ba2935649e785c01b33161a2533f0cfc287e11c2",
      "parents": [
        "4f599bae27e4aa4a4eb743b51cf017662278c36e"
      ],
      "author": {
        "name": "Chao Yu",
        "email": "chao@kernel.org",
        "time": "Mon Jun 15 09:05:58 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Jun 16 14:18:42 2026"
      },
      "message": "f2fs/009: use common _scratch_shutdown helper\n\nf2fs has supported ioctl(_IOR (\u0027X\u0027, 125, uint32_t)), so that\n\"f2fs_io shutdown\" can be completely replaced w/ _scratch_shutdown(),\nlet\u0027s clean up in f2fs/009.\n\nSuggested-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "4f599bae27e4aa4a4eb743b51cf017662278c36e",
      "tree": "bf59ca027c2b713194161b5fd762db27196c632a",
      "parents": [
        "6c5d1992fb3bcb6adf5c38eb31924d76794ae9dc"
      ],
      "author": {
        "name": "Chao Yu",
        "email": "chao@kernel.org",
        "time": "Tue Jun 16 07:35:26 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Jun 16 14:09:33 2026"
      },
      "message": "f2fs/025: test to do sanity check section type correctly in f2fs GC\n\nWithout commit 520760b9f915 (\"f2fs: optimize representative type determination\nin GC\"), f2fs GC will report inconsistent segment type in large section issue,\nand then it will force to shutdown filesystem.\n\n[  768.190903] F2FS-fs (loop51): Inconsistent segment (3) type [1, 0] in SIT and SSA\n\nThe reason is f2fs kernel will assume all segment type inside large section is\nthe same, during GC it loads type from one segment and compare it to other\nsegments\u0027 type, however due to recovery flow, the chosen segment may has zero\nvalid blocks w/ different segment type, since the segment is invalid(free) one,\nit will never be migrated, so that we should not treat such state as abnormal\ncondition.\n\nThis testcase is created to simulate above condition to see whether f2fs kernel\nmodule can handle it correctly\n\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "6c5d1992fb3bcb6adf5c38eb31924d76794ae9dc",
      "tree": "6bb11e61a88bd3228a18797c4b10fd9549b123ae",
      "parents": [
        "ec6d49da5d27690f8146a5fbbea9214abaa8a4cc"
      ],
      "author": {
        "name": "Shin\u0027ichiro Kawasaki",
        "email": "shinichiro.kawasaki@wdc.com",
        "time": "Mon Jun 15 12:12:57 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Jun 15 20:26:55 2026"
      },
      "message": "xfs/013: fix ENOSPC handling\n\nCommit 000813899afb (\"fstests: scale some tests for high CPU count\nsanity\") replaced \"touch\" with \"echo -n \u003e\" to speed up file creation by\nusing a shell builtin redirection instead of forking and execing an\nexternal binary. However, this broke the ENOSPC filtering the test\nrelies on.\n\nWhen the scratch filesystem fills up, the shell redirection \"\u003e $dir/$i\"\nfails instead of the \"touch\" command. The shell applies redirections\nleft-to-right, so \"\u003e $dir/$i\" is attempted before \"2\u003e\u00261\". Because\nopening the file fails immediately with ENOSPC, the command never runs\nand the shell writes the error message \"No space left on device\" to the\nstderr instead of the pipe. Then the error message is not passed to\n\"filter_enospc\" and leaks into the test output, causing the test case\nfailure. The failure is recreated by running the test case with rather\nsmall size of block devices, such as 128MiB null_blk:\n\nxfs/013            - output mismatch (see /home/test/xfstests/results//xfs/013.out.bad)\n    --- tests/xfs/013.out\t2026-05-28 16:52:16.881159200 +0900\n    +++ /home/test/xfstests/results//xfs/013.out.bad\t2026-06-11 17:20:36.269003467 +0900\n    @@ -5,3 +5,12305 @@\n     naming   \u003dVERN bsize\u003dXXX\n     log      \u003dLDEV bsize\u003dXXX blocks\u003dXXX\n     realtime \u003dRDEV extsz\u003dXXX blocks\u003dXXX, rtextents\u003dXXX\n    +/home/test/xfstests/tests/xfs/013: line 45: /var/scratch/dir2/19013: No space left on device\n    +/home/test/xfstests/tests/xfs/013: line 45: /var/scratch/dir2/6452: No space left on device\n    +/home/test/xfstests/tests/xfs/013: line 45: /var/scratch/dir2/14964: No space left on device\n    +/home/test/xfstests/tests/xfs/013: line 45: /var/scratch/dir2/10051: No space left on device\n    ...\n    (Run \u0027diff -u /home/test/xfstests/tests/xfs/013.out /home/test/xfstests/results//xfs/013.out.bad\u0027  to see the entire diff)\n\nTo fix the ENOSPC handling, wrap the redirection in a brace group so\nthat \"2\u003e\u00261\" is applied to the group before the inner redirection is\nattempted. The redirection failure is then written to the group\u0027s\nstderr, which is piped into \"filter_enospc\". This keeps the faster\nbuiltin file creation than the \"touch\" command as the trigger commit\nintended.\n\nFixes: 000813899afb (\"fstests: scale some tests for high CPU count sanity\")\nSigned-off-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "ec6d49da5d27690f8146a5fbbea9214abaa8a4cc",
      "tree": "79141b3d12724f96778cbf455ec6ce89459c8932",
      "parents": [
        "973512e9c24062257ec456e929232a8d6c0cb4e7"
      ],
      "author": {
        "name": "Yao Sang",
        "email": "sangyao@kylinos.cn",
        "time": "Fri Jun 12 07:42:31 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sun Jun 14 16:26:11 2026"
      },
      "message": "xfs: test zoned realtime writeback EIO shutdown\n\nCreate a zoned realtime filesystem with a single user data open zone,\ndirty one zone worth of data, and inject a writeback error on the\nrealtime device.\n\nAfter disabling fault injection, fsync a second write.  The filesystem\nmust already be shut down so that the second fsync fails quickly instead\nof waiting for zoned allocation progress.\n\nSigned-off-by: Yao Sang \u003csangyao@kylinos.cn\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "973512e9c24062257ec456e929232a8d6c0cb4e7",
      "tree": "3c84264e6685c3158388ea1da2d11422ea164a54",
      "parents": [
        "ace8d9c9dee5d6bf762cbf794f2d8d0e07fec3f0"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Thu May 28 10:27:07 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sun Jun 14 15:27:55 2026"
      },
      "message": "generic: add a test case for writes with prealloc extents beyond i_size\n\nTest writing into a file range containing prealloc extents beyond the current\ni_size, with an unmount and mount after fallocate and the write, to verify\nthat the file data, size and extent layout were not lost.\n\nThis used to fail on btrfs when not using the no-holes feature (which is\na default since btrfs-progs 5.15) before this recent kernel fix:\n\n   080ecbd05432 (\"btrfs: mark file extent range dirty after converting prealloc extents\")\n\nSo in order to reproduce the failure when using an unpatched kernel and\na btrfs-progs \u003e\u003d 5.15, one must run the test with:\n\n   MKFS_OPTIONS\u003d\"-O ^no-holes\"\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Qu Wenruo \u003cwqu@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "ace8d9c9dee5d6bf762cbf794f2d8d0e07fec3f0",
      "tree": "3c51a994a6787d58e9b586c1d95e172a6b00cba3",
      "parents": [
        "120ff814a4c98cd303e838ac6604b5816ab1600b"
      ],
      "author": {
        "name": "Qu Wenruo",
        "email": "wqu@suse.com",
        "time": "Sun Jun 07 23:38:01 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sun Jun 14 09:13:23 2026"
      },
      "message": "fstests: btrfs/138: add requirement for datacsum\n\n[FALSE ALERT]\nIf one has specified \"-o nodatasum\" as mount options, the test case\nbtrfs/138 will fail with the following error:\n\n MOUNT_OPTIONS -- -o nodatasum /dev/mapper/test-scratch1 /mnt/scratch\n\n btrfs/138    34s ... - output mismatch (see /home/adam/xfstests/results//btrfs/138.out.bad)\n    --- tests/btrfs/138.out\t2022-05-11 11:25:30.743333331 +0930\n    +++ /home/adam/xfstests/results//btrfs/138.out.bad\t2026-06-08 09:04:30.627143086 +0930\n    @@ -1,2 +1,5 @@\n     QA output created by 138\n    +ERROR: failed to set compression for /mnt/scratch/zlib: Invalid argument\n    +ERROR: failed to set compression for /mnt/scratch/lzo: Invalid argument\n    +ERROR: failed to set compression for /mnt/scratch/zstd: Invalid argument\n     Silence is golden\n    ...\n\n[CAUSE]\nBtrfs compression requires both datacow and datasum, thus nodatasum\nmount option will reject compression completely, causing the above\nfailures.\n\n[FIX]\nAdd _require_btrfs_no_nodatasum for the test case, so that for nodatasum\nmount option the test case can be properly skipped other than causing\nfalse failure.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "120ff814a4c98cd303e838ac6604b5816ab1600b",
      "tree": "143ffd00be697e5023f7068b488fe4a5aa7ce1b6",
      "parents": [
        "1104c45b26d01d40a187ed4c9f0517bebdc12b27"
      ],
      "author": {
        "name": "Christoph Hellwig",
        "email": "hch@lst.de",
        "time": "Tue Jun 09 08:00:44 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Thu Jun 11 18:03:32 2026"
      },
      "message": "xfs: test that a grown RT section can be filled\n\nThis reproduces issues with zoned growfs.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Hans Holmberg \u003chans.holmberg@wdc.com\u003e\nReviewed-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "1104c45b26d01d40a187ed4c9f0517bebdc12b27",
      "tree": "f7939d7da7e7a7a0d3328759ec251a75b5f53a2e",
      "parents": [
        "5d68212a7373f675fcff8b82082a0a64b04ae985"
      ],
      "author": {
        "name": "Christoph Hellwig",
        "email": "hch@lst.de",
        "time": "Tue Jun 09 08:00:43 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Thu Jun 11 18:00:49 2026"
      },
      "message": "common: add a _require_external_realtime_device helper\n\nFactor out the check for an RT device on an external section.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Hans Holmberg \u003chans.holmberg@wdc.com\u003e\nReviewed-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "5d68212a7373f675fcff8b82082a0a64b04ae985",
      "tree": "46a584495430ab905ded59adaa05464fa86588a5",
      "parents": [
        "80d250af40caf7d0db95caaf7243deefb16ef9a6"
      ],
      "author": {
        "name": "Shin\u0027ichiro Kawasaki",
        "email": "shinichiro.kawasaki@wdc.com",
        "time": "Wed Jun 03 05:27:06 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat Jun 06 19:59:35 2026"
      },
      "message": "common/filestreams: check zoned device before mkfs with small dsize\n\nThe test case xfs/170 performs file stream tests and must be skipped for\nzoned scratch devices since the filestream feature is not supported. The\ntest calls _require_xfs_scratch_non_zoned() to check if the scratch\ndevice is zoned.\n\nThis check is done after _try_scratch_mkfs_xfs() with a small dsize\nparameter. However, mkfs.xfs creates an inode for each zone, and when a\nzoned device has many zones, the small dsize causes metadata area\nshortage and mkfs fails. This unexpected failure causes the test to fail\neven though it should be skipped for zoned devices.\n\nMove the zoned device check to occur before the constrained mkfs. First\nperform a usual mkfs without the small dsize parameter to ensure the\ndevice can be properly checked for zoned mode, then verify it\u0027s non-\nzoned before proceeding with the small dsize mkfs.\n\nSigned-off-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "80d250af40caf7d0db95caaf7243deefb16ef9a6",
      "tree": "f32db26cc39751604ae159d656c337642210e8e8",
      "parents": [
        "26c2b701724afe41ec7e925549c883abf570b4f9"
      ],
      "author": {
        "name": "Qu Wenruo",
        "email": "wqu@suse.com",
        "time": "Tue Jun 02 10:39:03 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat Jun 06 19:58:09 2026"
      },
      "message": "fstests: btrfs: add a new test case for fstrim crash\n\nThere is a bug report that btrfs/242 can crash very randomly.\n\nIt turns out the crash is caused by a re-appearing missing device, which\nscrewed up several checks in fstrim.\n\nThis new test case is a more reliable version, dedicated for such crash,\nwhich will:\n\n- Create a raid1 btrfs\n- Mount with a single device in degraded mode\n- Let the missing device to re-appear\n- Run fstrim\n\nWhich is reliably crashing in my environment without the submitted fix.\nAnd with the submitted fix, the test no longer crashes.\n\nReported-by: Su Yue \u003cglass.su@suse.com\u003e\nLink: https://lore.kernel.org/linux-btrfs/wlwir19t.fsf@damenly.org/\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "26c2b701724afe41ec7e925549c883abf570b4f9",
      "tree": "471ae13303f61e17d553145e145c7bf17cba7b0e",
      "parents": [
        "d65330dd7de46410342e7b7000d7bbceb903de0d"
      ],
      "author": {
        "name": "Boris Burkov",
        "email": "boris@bur.io",
        "time": "Wed May 13 00:43:34 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 29 09:57:16 2026"
      },
      "message": "btrfs: test qgroup deletion races with squota writes\n\nWhen using simple quotas, an extent\u0027s EXTENT_OWNER_REF can long outlive\nthe subvolume that created it, since the extent can pick up additional\nreferences that keep it alive after the owning subvolume is deleted.\n\nSeveral lifecycle bugs around the owning qgroup arise from this:\n\n  1. Freeing an extent whose owner qgroup is gone: must not cause an\n     underflow nor a transaction abort.\n\n  2. Creating an extent in the same transaction that the owner subvolume\n     is deleted: the qgroup may already be gone by the time the squota\n     delta is recorded, leaving behind an EXTENT_OWNER_REF that points\n     at a qgroup that never accumulated a usage delta.  Manually\n     re-creating that qgroup and then freeing the extent would underflow\n     it.\n\n  3. Destroying a live subvolume\u0027s qgroup while delayed refs for newly\n     allocated tree blocks have not yet flushed: rfer/excl read as 0,\n     so the destroy looked safe, but the alloc delta was silently lost.\n\n  4. Destroying the qgroup of a live subvolume whose data predates\n     \u0027btrfs quota enable --simple\u0027: pre-existing extents are not\n     accounted (generation \u003c qgroup_enable_gen), so rfer/excl stay 0\n     permanently and a usage-only check happily destroys a qgroup\n     belonging to a still-mounted, still-writeable subvolume.\n\nAdd four cases covering these scenarios.  On a fixed kernel all four\n\u0027qgroup destroy\u0027 (and the re-create in case 2) operations are refused\nbecause the subvol check rejects the request; on an unfixed kernel\nthey would succeed and leave the filesystem with broken accounting or\ntrigger a transaction abort.\n\nSigned-off-by: Boris Burkov \u003cboris@bur.io\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "d65330dd7de46410342e7b7000d7bbceb903de0d",
      "tree": "8ba9dc1da79d40f27b3f9c25b6e404a4edc22554",
      "parents": [
        "239cc1d598663b849b5da29c5f9d0382ec8eb442"
      ],
      "author": {
        "name": "Boris Burkov",
        "email": "boris@bur.io",
        "time": "Wed May 13 00:43:33 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 29 09:52:51 2026"
      },
      "message": "btrfs: inline enable_quota helper in test 301\n\nThe enable_quota helper in btrfs/301 takes a mode argument (\u0027n\u0027, \u0027s\u0027,\nor anything else) to switch between \"no quota\", \"simple quota\", and\n\"full quota\" enable.  Only the simple-quota path is ever exercised by\nthis test, so the dispatch is dead weight and the indirection just\nobscures the actual btrfs command being run.\n\nInline the two call sites to call \u0027btrfs quota enable --simple\u0027\ndirectly and drop the helper.\n\nSigned-off-by: Boris Burkov \u003cboris@bur.io\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "239cc1d598663b849b5da29c5f9d0382ec8eb442",
      "tree": "58453dfec87bb493cd1a7c51994f005754401bd4",
      "parents": [
        "1418baaef1faa80d8f2203a2e8cbb36b86afb322"
      ],
      "author": {
        "name": "Qu Wenruo",
        "email": "wqu@suse.com",
        "time": "Thu May 28 11:16:59 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 29 09:13:01 2026"
      },
      "message": "fstests: cleanup old files to respect mount options needing new inodes\n\n[BUG]\nTest case generic/362 and generic/365 will fail with nodatasum, but\nthat\u0027s only when TEST_DEV is newly formatted.\n\n FSTYP         -- btrfs\n PLATFORM      -- Linux/x86_64 btrfs-vm 7.1.0-rc4-custom+ #381 SMP PREEMPT_DYNAMIC Tue May 26 10:47:14 ACST 2026\n MKFS_OPTIONS  -- -O bgt -K /dev/mapper/test-scratch1\n MOUNT_OPTIONS -- -o nodatasum /dev/mapper/test-scratch1 /mnt/scratch\n\n  generic/362  0s ... - output mismatch (see /home/adam/xfstests/results//generic/362.out.bad)\n    --- tests/generic/362.out\t2024-08-24 15:31:37.200000000 +0930\n    +++ /home/adam/xfstests/results//generic/362.out.bad\t2026-05-28 16:18:33.866141979 +0930\n    @@ -1,2 +1,3 @@\n     QA output created by 362\n    +First write failed: Input/output error\n     Silence is golden\n    ...\n    (Run \u0027diff -u /home/adam/xfstests/tests/generic/362.out /home/adam/xfstests/results//generic/362.out.bad\u0027  to see the entire diff)\n\n  generic/364  11s ... - output mismatch (see /home/adam/xfstests/results//generic/364.out.bad)\n    --- tests/generic/364.out\t2024-09-30 09:09:51.216666681 +0930\n    +++ /home/adam/xfstests/results//generic/364.out.bad\t2026-05-28 16:18:34.318532257 +0930\n    @@ -1,2 +1,3 @@\n     QA output created by 364\n    +Fsync failed: Input/output error\n     Silence is golden\n    ...\n    (Run \u0027diff -u /home/adam/xfstests/tests/generic/364.out /home/adam/xfstests/results//generic/364.out.bad\u0027  to see the entire diff)\n\nBut if one has formated TEST_DEV, run test with default mount option,\nthen change the mount option to \"nodatasum\", the test will not fail\nanymore:\n\n FSTYP         -- btrfs\n PLATFORM      -- Linux/x86_64 btrfs-vm 7.1.0-rc4-custom+ #381 SMP PREEMPT_DYNAMIC Tue May 26 10:47:14 ACST 2026\n MKFS_OPTIONS  -- -O bgt -K /dev/mapper/test-scratch1\n MOUNT_OPTIONS -- /dev/mapper/test-scratch1 /mnt/scratch\n\n generic/362  0s ...  1s\n generic/364  11s ...  10s\n Ran: generic/362 generic/364\n Passed all 2 tests\n\n FSTYP         -- btrfs\n PLATFORM      -- Linux/x86_64 btrfs-vm 7.1.0-rc4-custom+ #381 SMP PREEMPT_DYNAMIC Tue May 26 10:47:14 ACST 2026\n MKFS_OPTIONS  -- -O bgt -K /dev/mapper/test-scratch1\n MOUNT_OPTIONS -- -o nodatasum /dev/mapper/test-scratch1 /mnt/scratch\n\n generic/362  1s ...  0s\n generic/364  10s ...  11s\n Ran: generic/362 generic/364\n Passed all 2 tests\n\n[CAUSE]\nBtrfs\u0027 nodatasum mount option only affects new files, but the test cases\nare using TEST_DEV, and never delete the target files\n\"$TEST_DIR/dio-append-buf-fault\" for generic/362 and\n\"$TEST_DIR/dio-write-fsync-same-fd\" for generic/364.\n\nSo if the files are created with default mount options, then all later\n\"nodatasum\" mount options will not affect those files, thus hide the test\nfailure.\n\n[FIX]\nFor all test cases utilizing \"$here/src/dio*\", add a _cleanup()\nfunction, to remove target files, so that for mount options that only\naffect new inodes, the mount options will be respected, and expose\nfailures.\n\nNow generic/36[24] will properly fail for \"nodatasum\" mount option on\nbtrfs.\n\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "1418baaef1faa80d8f2203a2e8cbb36b86afb322",
      "tree": "b66ff68cfaee14f0a34012f9b258a89b8492f05f",
      "parents": [
        "c1dcfe62b3f95d323224e9b8087ab0e6df69c993"
      ],
      "author": {
        "name": "Qu Wenruo",
        "email": "wqu@suse.com",
        "time": "Sun May 24 05:08:48 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 29 08:54:30 2026"
      },
      "message": "fstests: btrfs: add a new test case for single data RAID56\n\nAlthough single-data-RAID56, aka 2 disks raid5 or 3 disks raid6, is\nnot recommended for btrfs, btrfs still supports it as there are cases\nlike degraded writes can still lead to such cases.\n\nBut we do not have any proper tests for such corner cases.\n\nFurthermore, RAID56 lib is going to drop the support of\nsingle-data-RAID56, and btrfs will have its own handling of such cases,\nthus coverage on single-data-RAID56 is required.\n\nThis new test case will have the following workload to verify the\nbehavior:\n\n- Create a fs with single-data-RAID56\n\n- Populate the fs with fsx and fsstress\n  Fsx and fsstress will utilize read and write paths of RAID56.\n\n- Mount each device in degraded mode and run read-only scrub on them\n  Such scrub will utilize the following path of RAID56:\n  * Regular data read\n  * Reconstruction read\n  * P/Q stripe scrub\n\n- Re-scan all devices and add a new disk to the array\n- Balance all data and scrub again\n  This should utilized non-single-data-RAID56 handling.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "c1dcfe62b3f95d323224e9b8087ab0e6df69c993",
      "tree": "0649a3ad5bc9bd5c0a10773b703e2a00041628b4",
      "parents": [
        "c5ddd1789ae14e1acd512f6cc2af61778ac53aa6"
      ],
      "author": {
        "name": "Andrey Albershteyn",
        "email": "aalbersh@kernel.org",
        "time": "Thu May 21 08:26:46 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 29 07:22:08 2026"
      },
      "message": "generic/791: don\u0027t run if kernel misses FANOTIFY\n\nIf FANOTIFY\u003dno in the kernel, then fs-monitor will fail to start. Fix\nfs-monitor error codes to detect and skip the test on \"Function not\nimplemented\" code.\n\nSigned-off-by: Andrey Albershteyn \u003caalbersh@kernel.org\u003e\nReviewed-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "c5ddd1789ae14e1acd512f6cc2af61778ac53aa6",
      "tree": "51805ff380b5450b44b0217a7fd649738a44635a",
      "parents": [
        "55d8071bc4a86895fadb5d7767ef1f016df7d010"
      ],
      "author": {
        "name": "Joanne Chang",
        "email": "joannechien@google.com",
        "time": "Wed May 13 03:20:09 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed May 20 10:42:32 2026"
      },
      "message": "f2fs/021: Fix mount syntax for disabling jquota\n\nF2FS has removed the trailing \"\u003d\" in the mount options for disabling\nuser journaled quotas. Update f2fs/021 to try the new syntax first and\nfall back to the legacy syntax if the initial mount attempt fails.\n\nSigned-off-by: Joanne Chang \u003cjoannechien@google.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "55d8071bc4a86895fadb5d7767ef1f016df7d010",
      "tree": "417f13e6b3929cbb835f64e84f38baebcab0a46f",
      "parents": [
        "d5fb5bbbd22d836cbb256480191632b485671dbe"
      ],
      "author": {
        "name": "Joanne Chang",
        "email": "joannechien@google.com",
        "time": "Wed May 13 03:20:08 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed May 20 10:42:32 2026"
      },
      "message": "f2fs/015: Fix mount syntax for disabling jquota\n\nF2FS has removed the trailing \"\u003d\" in the mount options for disabling\nuser, group, and project journaled quotas. To maintain compatibility,\nupdate the test cases in f2fs/015 to try the new syntax first, and fall\nback to the legacy syntax if the initial mount attempt fails.\n\nSigned-off-by: Joanne Chang \u003cjoannechien@google.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "d5fb5bbbd22d836cbb256480191632b485671dbe",
      "tree": "a3d8186c4484537cd5b1d4360e3a28e7b7ff5b9b",
      "parents": [
        "d66e76fc5ab6a6f1550b09aa6904d7974da3aad8"
      ],
      "author": {
        "name": "Viacheslav Dubeyko",
        "email": "slava@dubeyko.com",
        "time": "Thu May 14 20:00:05 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed May 20 10:38:38 2026"
      },
      "message": "common/rc: exclude HFS from atime testing\n\nHFS hasn\u0027t any field in on-disk layout that can keep\nthe file/folder access times (atime):\n\n/* The catalog record for a file */\nstruct hfs_cat_file {\n        s8 type;                        /* The type of entry */\n        u8 reserved;\n        u8 Flags;                       /* Flags such as read-only */\n        s8 Typ;                         /* file version number \u003d 0 */\n        struct hfs_finfo UsrWds;        /* data used by the Finder */\n        __be32 FlNum;                   /* The CNID */\n        __be16 StBlk;                   /* obsolete */\n        __be32 LgLen;                   /* The logical EOF of the data fork*/\n        __be32 PyLen;                   /* The physical EOF of the data fork */\n        __be16 RStBlk;                  /* obsolete */\n        __be32 RLgLen;                  /* The logical EOF of the rsrc fork */\n        __be32 RPyLen;                  /* The physical EOF of the rsrc fork */\n        __be32 CrDat;                   /* The creation date */\n        __be32 MdDat;                   /* The modified date */\n        __be32 BkDat;                   /* The last backup date */\n        struct hfs_fxinfo FndrInfo;     /* more data for the Finder */\n        __be16 ClpSize;                 /* number of bytes to allocate\n                                           when extending files */\n        hfs_extent_rec ExtRec;          /* first extent record\n                                           for the data fork */\n        hfs_extent_rec RExtRec;         /* first extent record\n                                           for the resource fork */\n        u32 Resrv;                      /* reserved by Apple */\n} __packed;\n\nThis patch disable the generic/003 and atime related test-cases for\nHFS file system.\n\nSigned-off-by: Viacheslav Dubeyko \u003cslava@dubeyko.com\u003e\ncc: John Paul Adrian Glaubitz \u003cglaubitz@physik.fu-berlin.de\u003e\ncc: Yangtao Li \u003cfrank.li@vivo.com\u003e\ncc: linux-fsdevel@vger.kernel.org\ncc: fstests@vger.kernel.org\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "d66e76fc5ab6a6f1550b09aa6904d7974da3aad8",
      "tree": "301eefd778e0450e3076a042f16337d63ce541f3",
      "parents": [
        "32b4dfffbc086df51c7a16ee59086da8e5024bc6"
      ],
      "author": {
        "name": "Jan Prusakowski",
        "email": "jprusakowski@google.com",
        "time": "Fri May 15 08:26:08 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed May 20 10:26:37 2026"
      },
      "message": "generic/563: allow read tolerance for f2fs in scenario 3\n\nF2FS is a log-structured file system that allocates new blocks even for\noverwrites. To perform allocation, it may need to read metadata blocks\n(such as the Node Address Table (NAT) or Segment Info Table (SIT)) if\nthey are not already in memory.\n\nIn scenario 3 (read -\u003e read/write), unlike scenario 2, there is no prior\nwrite in the same mount session to load these metadata blocks into memory.\nTherefore, the write operation in the second cgroup triggers metadata\nreads, which are charged to that cgroup.\n\nRelax the read tolerance for f2fs in scenario 3 to accommodate these\nexpected metadata reads, matching the tolerance already used in scenario 2.\n\nSigned-off-by: Jan Prusakowski \u003cjprusakowski@google.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "32b4dfffbc086df51c7a16ee59086da8e5024bc6",
      "tree": "045eaf6dc7d09fb98f15cac9d23fa7fe2b9921cc",
      "parents": [
        "ce4e96a89a2b876497006b3fcbb388ee41f7aa8a"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Tue May 19 17:14:10 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed May 20 09:42:06 2026"
      },
      "message": "generic: add a test case for fallocate i_size extension\n\nTest an i_size expanding fallocate into a range beyond current i_size that\nalready has a preallocated extent, with an unmount and mount after each\nfallocate to verify that no metadata (i_size) and extents were lost.\n\nThis used to fail on btrfs when not using the no-holes feature (which is\na default since btrfs-progs 5.15) before this recent kernel fix:\n\n  c562ba61fc5e (\"btrfs: fix incorrect i_size after remount caused by KEEP_SIZE prealloc gap\")\n\nSo in order to reproduce the failure when using an unpatched kernel and\na btrfs-progs \u003e\u003d 5.15, one must run the test with:\n\n  MKFS_OPTIONS\u003d\"-O ^no-holes\"\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: Qu Wenruo \u003cwqu@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "ce4e96a89a2b876497006b3fcbb388ee41f7aa8a",
      "tree": "4bf13b60cfec61124be7bd0ff9b6d2527072c472",
      "parents": [
        "748ae5ab407610b1e3fa706c354016cf035e82ec"
      ],
      "author": {
        "name": "Christoph Hellwig",
        "email": "hch@lst.de",
        "time": "Mon May 18 06:24:53 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed May 20 09:41:20 2026"
      },
      "message": "generic: add a test that stresses metadata eviction\n\nThe fsverity test generic/579 could be used to reproduce a regression in\nthe xfs buffer hashing.  Carlos Maiolino figured out that even removing\nthe fsverity-specific bits would reproduce the issue.  This test is\nthus a copy of generic/579 with the fsverity bits striped out, and\nrun 5 times as that seems to be the threshold at which the issue\nreproduces reliably.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "748ae5ab407610b1e3fa706c354016cf035e82ec",
      "tree": "8e2e07fdcc67c7037e9302d6ea04eb41e548ad77",
      "parents": [
        "ffc8bad17e5b2f56e48dbac43f7c5ae8ac368fe5"
      ],
      "author": {
        "name": "Qu Wenruo",
        "email": "wqu@suse.com",
        "time": "Thu May 14 09:04:39 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sun May 17 08:11:33 2026"
      },
      "message": "btrfs/340: add support for older kernels/progs\n\nThe test case will fail on older distros like SLE12-SP5, there are two\nproblems on the test case itself:\n\n- Requires \"--sync\" option from \"btrfs qgroup show\" subcommand\n  That option was introduecd in v4.9.1, thus there are still some older\n  distros using that very old version.\n\n- Not all kernels support quick inherit\n  The kernel commit introducing the quick inherit is 6.9, thus some\n  supported LTS kernels do not have that commit.\n\n  In that case qgroup will just be marked inconsistent, this will cause\n  the later \"btrfs qgroup show\" command to output a warning due to the\n  inconsistent flag.\n\nFix both problems by:\n\n- Require \"--sync\" option from \"btrfs qgroup show\" subcommand\n  So older distros will just skip the test.\n\n- Redirect all output from \"btrfs qgroup show\" to $seqres.full\n  So older kernels can still pass the test case by marking qgroup\n  inconsitent.\n\nReported-by: Long An \u003clan@suse.com\u003e\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "ffc8bad17e5b2f56e48dbac43f7c5ae8ac368fe5",
      "tree": "907d2844388cd8c2da36db4f29160717662f488c",
      "parents": [
        "393a4e58584dccbbc457aa7f16a315175bdaa474"
      ],
      "author": {
        "name": "Lukas Herbolt",
        "email": "lukas@herbolt.com",
        "time": "Thu May 14 11:39:15 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 15 16:20:23 2026"
      },
      "message": "xfs/21{6,7} Use default -l concurrency\u003d0 on mkfs.xfs that supports it\n\nThe XFS concurrency optimization breaks the log sizing check on\nsystems with non-rotational disks and high amount of CPUs. Default to\nthe old behavior with -l concurrency\u003d0 and with -d concurrency\u003d0.\n\nSigned-off-by: Lukas Herbolt \u003clukas@herbolt.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "393a4e58584dccbbc457aa7f16a315175bdaa474",
      "tree": "6ca86687e41c07ae5b7d362c653d691e76778612",
      "parents": [
        "7f162f5bcf50fc32c7e3b432e7ff189571a3151f"
      ],
      "author": {
        "name": "Lukas Herbolt",
        "email": "lukas@herbolt.com",
        "time": "Thu May 14 11:39:13 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 15 16:20:23 2026"
      },
      "message": "generic/{102,172,347}: Adapt test for XFS on systems with 128+CPUs + SSDs\n\nXFS will now scale by default its log size according the amount of CPUs. This\ncan significantly increase the log area and using hard-coded size of file size\nwill make the test file. Using the X percent of the free space to create the\nfile will let the test proceed.\n\nFor generic/102 we also have to change the 102.out as we cannot know the\namount written data and it has to be filtered out.\n\nFor generic/172 we just use the new function to calculate file big enough\nto consume most of the available space.\n\nThe generic/347 will use -l concurrency\u003d0 in case it is being run on the\nXFS filesystem and mkfs.xfs already supports this option.\n\nSigned-off-by: Lukas Herbolt \u003clukas@herbolt.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "7f162f5bcf50fc32c7e3b432e7ff189571a3151f",
      "tree": "90d90be08e3ea2a23865bdf443026b6d105f2b1d",
      "parents": [
        "55f45a620c552ec77e69291f58b89c27a972ba9a"
      ],
      "author": {
        "name": "Lukas Herbolt",
        "email": "lukas@herbolt.com",
        "time": "Thu May 14 11:39:11 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 15 16:20:23 2026"
      },
      "message": "common/xfs: helper function to check if -l/-d/-r concurrecy flags.\n\nCheck if the requested flag is supported by the mkfs.xfs on scratch\ndevice.\n\nSigned-off-by: Lukas Herbolt \u003clukas@herbolt.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "55f45a620c552ec77e69291f58b89c27a972ba9a",
      "tree": "18c616ac1585b8cbf5336c3d2791278fecfa014c",
      "parents": [
        "8c69a37c4f4c32f49957bc9720e11304de6fca33"
      ],
      "author": {
        "name": "Lukas Herbolt",
        "email": "lukas@herbolt.com",
        "time": "Thu May 14 11:39:09 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 15 16:20:23 2026"
      },
      "message": "common/rc: Add helper to calculate percentage of free space available\n\nIt calculates percentage of filesystem available space and returns it\nin MB. This helper will be used in the following test/generic fixes.\n\nSigned-off-by: Lukas Herbolt \u003clukas@herbolt.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "8c69a37c4f4c32f49957bc9720e11304de6fca33",
      "tree": "369c2655537ba76da11bfad19dbf2911cf03b1cc",
      "parents": [
        "4192c9e2266c8e92b49e3f73fe505101ab36ce1b"
      ],
      "author": {
        "name": "Christian Brauner",
        "email": "brauner@kernel.org",
        "time": "Mon Mar 23 13:32:15 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue May 12 17:22:35 2026"
      },
      "message": "vfs: fix dumpable race in create_userns_hierarchy()\n\nAll processes in the userns hierarchy share the same mm_struct due to\nCLONE_VM. When a child calls setresuid() in switch_ids(), the kernel\nclears the dumpable flag on the shared mm. The child immediately\nre-sets it via prctl(PR_SET_DUMPABLE, 1), but there is a window\nbetween the two where the parent may be opening /proc/PID/ns/user for\nthe previous level\u0027s child. That open hits ptrace_may_access() which\nchecks get_dumpable(mm) and, finding it zero, falls back to\nptrace_has_cap(mm-\u003euser_ns, mode). Since mm-\u003euser_ns is init_user_ns\n(the mm was created by real root) and the parent is only ns-root, the\ncapability check fails and the open returns -EACCES.\n\nFix this by extending the existing two-way socketpair handshake into a\nthree-way handshake: the child signals the parent after becoming\ndumpable, then blocks until the parent has opened /proc/PID/ns/user\nand signals back. Only then does the child proceed to\ncreate_userns_hierarchy() for the next level. This guarantees no\nconcurrent setresuid() can clear dumpable while the parent\u0027s open() is\nin flight.\n\nSigned-off-by: Christian Brauner \u003cbrauner@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "4192c9e2266c8e92b49e3f73fe505101ab36ce1b",
      "tree": "3dbb1897bc99098a0b03f6d2cdcd099613afcd6e",
      "parents": [
        "0d6ed520323d82dbb0f9ad77a7a63e48d01a3c4e"
      ],
      "author": {
        "name": "David Disseldorp",
        "email": "ddiss@suse.de",
        "time": "Mon Mar 23 04:45:58 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue May 12 17:22:03 2026"
      },
      "message": "common/rc: add default _udev_wait timeout\n\nIf udevd isn\u0027t running then \"udevadm wait\" loops endlessly. With a\n--timeout parameter provided, udevadm (udev-254.27) prints to stderr:\n  Timed out for waiting devices being initialized.\n\nThe error message causes test failure via golden output mismatch and\nis easier to debug than an infinite loop.\n\nThe timeout parameter is also compatible with existing\nargs\u003d\"--removed \u003cdev\u003e\" callers. 60 seconds is relatively arbitrary, but\nshould be long enough to avoid premature timeout on regular systems.\n\nSigned-off-by: David Disseldorp \u003cddiss@suse.de\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "0d6ed520323d82dbb0f9ad77a7a63e48d01a3c4e",
      "tree": "f70165a230fb7e777b6fc15b4c9843ffa8751bda",
      "parents": [
        "3aca6733f6cd93cbf000b7dbfc8af128796e2425"
      ],
      "author": {
        "name": "Ojaswin Mujoo",
        "email": "ojaswin@linux.ibm.com",
        "time": "Wed Apr 01 10:09:41 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue May 12 17:13:30 2026"
      },
      "message": "ext4/307: Calculate donor size to avoid failures for 64k bs\n\nCalculating size of donor file based on du output causes the following\nissue:\n\ne4compact.c:68: do_defrag_range: Assertion `donor-\u003elength \u003e\u003d len\u0027 failed.\n./common/rc: line 4616: 1583182 Aborted                 (core dumped)\n\nThe issue is that e4compat asserts that the stat.st_size of all files\ncombined shouldn\u0027t be more than that of the donor file. In case of 64k\nblocksize, fsstress often creates sparse files which have \u003e3G size even\nthough their disk utilization is \u003c100M. Since donor file is not big\nenough, this trips e4compat causing the failure.\n\nFix this by using stat.st_size rather than du value to get the size.\nAlso, make some changes to avoid future ENOSPC like reducing the -n\npassed to fsstress to keep the size around 2G and making sure we use the\nwhole SCRATCH disk instead of 500M.\n\nWhile we are at it, add some new lines to make the code bit more\nreadable.\n\nReported-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nTested-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "3aca6733f6cd93cbf000b7dbfc8af128796e2425",
      "tree": "f7ed0a686bdf4c7aeef2feec83c27ff3899a9b56",
      "parents": [
        "a974318c5bfa1debda2f0ce18fccb1ea336dcfbb"
      ],
      "author": {
        "name": "Disha Goel",
        "email": "disgoel@linux.ibm.com",
        "time": "Fri May 08 14:47:01 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon May 11 16:18:14 2026"
      },
      "message": "btrfs/291: fix state transition logic and add size requirement\n\nThis patch fixes two issues in btrfs/291:\n\n1. Add dynamic LOGWRITES_DEV size requirement based on SCRATCH_DEV\n   The test creates LVM snapshots at each FUA point during replay,\n   requiring significant space. Calculate the required size as 120%\n   of SCRATCH_DEV size (adding 20% overhead for LVM snapshots and\n   metadata) to ensure the test works regardless of SCRATCH_DEV size.\n\n2. Fix state transition logic for verity enablement\n   The original test assumed orphan items would always be created\n   during verity enablement (state 0-\u003e1 transition). However, in\n   some cases verity completes without creating orphan items,\n   causing the test to fail with \"expected to reach verity done state\".\n\n   Fix by transitioning to state 1 when either orphan items exist\n   OR merkle items appear, handling both verity enablement paths.\n   Also improve state 1 validation to only check for cleared merkle\n   items when measurement actually fails.\n\nThe test now correctly handles verity enablement with or without\norphan items while maintaining crash consistency validation, and\nworks with any SCRATCH_DEV size.\n\nSuggested-by: Anand Jain \u003canajain.sg@gmail.com\u003e\nSigned-off-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "a974318c5bfa1debda2f0ce18fccb1ea336dcfbb",
      "tree": "b8e953853944022b0e9f114ad702415aa6fcd78f",
      "parents": [
        "8413f58d843f88c5132474297e5cbfac5ba6dad5"
      ],
      "author": {
        "name": "Disha Goel",
        "email": "disgoel@linux.ibm.com",
        "time": "Fri May 08 14:47:00 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon May 11 16:18:14 2026"
      },
      "message": "common/dmlogwrites: add _require_log_writes_sized helper\n\nAdd a new helper function _require_log_writes_sized() to check if the\nLOGWRITES_DEV meets a minimum size requirement.\n\nThis is useful for tests that use dm-log-writes with additional space\nrequirements, such as creating LVM snapshots during log replay or tests\nthat generate large amounts of logged I/O operations.\n\nThe function takes a size parameter in KB, calls _require_log_writes()\ninternally, and skips the test if LOGWRITES_DEV is smaller than the\nrequired size.\n\nSuggested-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSuggested-by: Anand Jain \u003canajain.sg@gmail.com\u003e\nSigned-off-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "8413f58d843f88c5132474297e5cbfac5ba6dad5",
      "tree": "e49c5ec2aa8bec43ad73b1c20c69ae0d26126013",
      "parents": [
        "b8bcadc36c3624fad6f6a2b8bdc407ae2a88b496"
      ],
      "author": {
        "name": "Qu Wenruo",
        "email": "wqu@suse.com",
        "time": "Sun May 10 00:17:04 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sun May 10 19:10:23 2026"
      },
      "message": "fstests: support new mkfs.btrfs help string\n\n[BUG]\nThe latest btrfs-progs release v7.0 breaks a lot of tests, e.g.\nbtrfs/003:\n\nbtrfs/003    55s ... [failed, exit status 1]- output mismatch (see /home/kts/kernel-test-suite/src/xfstests/results//btrfs/003.out.bad)\n    --- tests/btrfs/003.out     2026-05-09 03:07:52.952213772 +0900\n    +++ /home/kts/kernel-test-suite/src/xfstests/results//btrfs/003.out.bad     2026-05-09 23:32:17.595751435 +0900\n    @@ -1,2 +1,3 @@\n     QA output created by 003\n    -Silence is golden\n    +mkfs failed\n    +(see /home/kts/kernel-test-suite/src/xfstests/results//btrfs/003.full for details)\n    ...\n    (Run \u0027diff -u /home/kts/kernel-test-suite/src/xfstests/tests/btrfs/003.out /home/kts/kernel-test-suite/src/xfstests/results//btrfs/003.out.bad\u0027  to see the entire diff)\n\n[CAUSE]\nCommit ec8324cc4b8b (\"btrfs-progs: help: adjust alignment of text\") from\nbtrfs-progs changed the helpe string output format, the previous help\nstring for \"-f\" option of mkfs.btrfs looks like this:\n\n    -f|--force                force overwrite of existing filesystem\n\nThere were 4 spaces before the \"-f\", thus can be matched by\n\"[[:space:]]-f[[:space]|,]\".\n\nBut now the help string looks like:\n\n-f, --force               force overwrite of existing filesystem\n\nWhich removed the spaces at the beginning.\n\nThe existing regex to catch \"-f\" requires at least one space before\n\"-f\", now it doesn\u0027t match the new btrfs help string, and cause mkfs\nfailure because we can not overwrite an existing scratch device without\n\"-f\" option.\n\n[FIX]\nChange the regex to allow no space before \"-f\".\n\nReported-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nLink: https://lore.kernel.org/linux-btrfs/af9EHC5b-aBdr1zn@shinmob/\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "b8bcadc36c3624fad6f6a2b8bdc407ae2a88b496",
      "tree": "3e3f8738e57c375c52051c8b888f1f35e3d4244d",
      "parents": [
        "cdd9140a2f78951f077aafeb0f337c8a93a35026"
      ],
      "author": {
        "name": "Joanne Chang",
        "email": "joannechien@google.com",
        "time": "Tue Apr 28 02:24:40 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat May 09 16:51:09 2026"
      },
      "message": "f2fs/{022,023}: clear MOUNT_OPTIONS alongside MKFS_OPTIONS\n\nCurrently, f2fs/022 and f2fs/023 only clears MKFS_OPTIONS. This causes\nthe tests to fail when leftover MOUNT_OPTIONS depend on unapplied\nMKFS_OPTIONS. So MOUNT_OPTIONS should also be cleared to ensure reliable\nmounting.\n\nSigned-off-by: Joanne Chang \u003cjoannechien@google.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "cdd9140a2f78951f077aafeb0f337c8a93a35026",
      "tree": "3e3bec0311354236620818c9238f137ef002b1c8",
      "parents": [
        "f61ba0fde3ec9cdfd7eed711aca2b28e973c2905"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Thu May 07 22:23:34 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat May 09 16:51:03 2026"
      },
      "message": "generic/45[34]: don\u0027t warn on mixed bidirectional characters\n\nWe\u0027re dropping this warning from xfs_scrub because the warning is\nincorrect, so let\u0027s make sure the QA system checks that it\u0027s gone.\n\nCc: gedalya@gedalya.net\nSigned-off-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "f61ba0fde3ec9cdfd7eed711aca2b28e973c2905",
      "tree": "e68d2e20cb5d9a66cc84c3b8a9adb18f86402b19",
      "parents": [
        "528c7ba2a275d4e4b592145acd4366158af48cbc"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Thu May 07 22:23:19 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat May 09 16:51:03 2026"
      },
      "message": "generic/45[34]: add detection of confusable variation sequences\n\nArsTechnica recently wrote about a GitHub supply chain attack wherein\nnon-rendering unicode sequences were embedded in javascript files to\nhide payloads that could be decrypted trivially later.  While these are\nunlikely to appear in file and attribute names, xfs_scrub will warn about\nthis sort of steganography, so let\u0027s make sure it works.\n\nSigned-off-by: \"Darrick J. Wong\" \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "528c7ba2a275d4e4b592145acd4366158af48cbc",
      "tree": "d1907f8da61f0b08f7be4c588fa5982d8efac922",
      "parents": [
        "12c729c1a296dcd799a217a26c433f9bf79477fa"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Mon May 04 16:09:57 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Thu May 07 20:25:16 2026"
      },
      "message": "fstests: add commit IDs for kernel fixes already merged\n\nA few fixes were merged into Linus\u0027 tree, so add their commit IDs in the\nrespective test cases.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "12c729c1a296dcd799a217a26c433f9bf79477fa",
      "tree": "b6529aa07eb8ca3be3823035bce105c35b32beb7",
      "parents": [
        "d9b1d9c6f43ee71cf16020afde63d453bf0468ac"
      ],
      "author": {
        "name": "Christoph Hellwig",
        "email": "hch@lst.de",
        "time": "Thu May 07 05:09:49 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Thu May 07 18:48:11 2026"
      },
      "message": "xfs/216: pass -t xfs to _mount\n\nWithout this, mount probes different file system type, which ended up\nexposing kernel bugs in blocksize \u003e PAGE_SIZE bugs in tons of\nlegacy file systems.  Bypass that by forcing XFS and making the\nmount a little more efficient.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nReviewed-by: Andrey Albershteyn \u003caalbersh@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "d9b1d9c6f43ee71cf16020afde63d453bf0468ac",
      "tree": "47adefba321f687c3a9f2c38153e2fdd4db8631d",
      "parents": [
        "95155ec233fad04d8701bfec74accefec691342c"
      ],
      "author": {
        "name": "Johannes Thumshirn",
        "email": "johannes.thumshirn@wdc.com",
        "time": "Wed Apr 29 20:46:24 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon May 04 02:57:17 2026"
      },
      "message": "generic/793: limit number of overwrites\n\nTestcase generic/793 overwrites a 1GB file \"number of sequential zones\"\ntimes in order to trigger a bug in zoned BTRFS\u0027 garbage collection. But on\nscratch devices with a huge number of sequential zones (like SMR drives)\nthis can cause very long runtimes.\n\nAs the testcase also limits the filesystem size to 16GB, constraint the\nnumber of overwrite loops to the number of sequential zones in the\nfilesystem. This still guarantees that the file will be overwritten often\nenough to trigger the bug while not exploding the overall test runtime.\n\nReported-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nReviewed-by: Hans Holmberg \u003chans.holmberg@wdc.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "95155ec233fad04d8701bfec74accefec691342c",
      "tree": "a240f4c8b6e8c445c5cb0e9fcead6efdd1fd8764",
      "parents": [
        "55e172c4c9144d2b944f0c03801b507f9e74c5ba"
      ],
      "author": {
        "name": "Zhang Yi",
        "email": "yi.zhang@huawei.com",
        "time": "Tue Apr 28 08:57:50 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 01 16:57:03 2026"
      },
      "message": "generic: test post-EOF gap zeroing persistence\n\nTest that extending a file past a non-block-aligned EOF correctly\nzero-fills the gap [old_EOF, block_boundary), and that this zeroing\npersists through a filesystem shutdown+remount cycle.\n\nStale data beyond EOF can persist on disk when append write data blocks\nare flushed before the on-disk file size update, or when concurrent\nappend writeback and mmap writes persist non-zero data past EOF.\nSubsequent post-EOF operations (append write, fallocate, truncate up)\nmust zero-fill and persist the gap to prevent exposing stale data.\n\nThe test pollutes the file\u0027s last physical block (via FIEMAP + raw\ndevice write) with a sentinel pattern beyond i_size, then performs each\nextend operation and verifies the gap is zeroed both in memory and on\ndisk.\n\nSigned-off-by: Zhang Yi \u003cyi.zhang@huawei.com\u003e\nReviewed-by: Brian Foster \u003cbfoster@redhat.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "55e172c4c9144d2b944f0c03801b507f9e74c5ba",
      "tree": "498f1fd316151df98c1a0c190850e455ad248be1",
      "parents": [
        "832a6d9ac226e017b41b052b89bfa2f66ac8c039"
      ],
      "author": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri Apr 17 18:08:39 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 01 15:49:22 2026"
      },
      "message": "xfs/227: fix bad variable expansion\n\nThe create_data() set cmd_str to \"-c \\\"resvsp $((off * 4096)) 4096\\\".\nThat cause xfs_io can\u0027t split the command line properly, it fails as:\n\n  command \"\"resvsp\" not found\n\nFixes: aaf40fb7 (\"fstests: xfs/227 is really slow\")\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "832a6d9ac226e017b41b052b89bfa2f66ac8c039",
      "tree": "9332ce123d79a85b2fc09a3d9591b6a37c880535",
      "parents": [
        "078f3204e049c8ffcf7819bab9afd419267d0084"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Thu Apr 16 19:15:43 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 01 15:42:41 2026"
      },
      "message": "check: capture dmesg of mount failures if test fails\n\nCapture the kernel output after a mount failure occurs.  If the test\nitself fails, then keep the logging output for further diagnosis.  The\nxunit.xsd update adds a \u003cmount-failure\u003e element to the xml output, whose\noutput is the mountfail file.\n\nNote that because the .mountfail file is preserved by ./check, the new\nselftest requires the user to check for the .mountfail file.  This is a\nlittle awkward.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "078f3204e049c8ffcf7819bab9afd419267d0084",
      "tree": "60510e19016a84be873400ba11c78ccd5e394987",
      "parents": [
        "cac9fe2b8dc3e6dbc0c2383b9e3b4d3c1b9e7dd0"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Mon Apr 13 17:51:09 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri May 01 15:40:16 2026"
      },
      "message": "treewide: convert all $MOUNT_PROG to _mount\n\nGoing to add some new log scraping functionality when mount failures\noccur, so we need everyone to use _mount instead of $MOUNT_PROG.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "cac9fe2b8dc3e6dbc0c2383b9e3b4d3c1b9e7dd0",
      "tree": "0da288dba10795ca83c4c71a750284632bb62677",
      "parents": [
        "d59865ddf8e4dc199e8b572fe8475abb621d6725"
      ],
      "author": {
        "name": "Johannes Thumshirn",
        "email": "johannes.thumshirn@wdc.com",
        "time": "Wed Apr 15 10:40:15 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Thu Apr 16 18:19:30 2026"
      },
      "message": "generic: test premature ENOSPC in zoned garbage collection\n\nThis test stresses garbage collection in zoned file systems by\nconstantly overwriting the same file. It is inspired by a reproducer\nfor a btrfs bugfix.\n\nSigned-off-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "d59865ddf8e4dc199e8b572fe8475abb621d6725",
      "tree": "f5ab17ab4d9314936a6e43661e8b5876f5fe51a9",
      "parents": [
        "dde983e4419abd83568e9c9ebb4b576848d48eb7"
      ],
      "author": {
        "name": "Christoph Hellwig",
        "email": "hch@lst.de",
        "time": "Tue Apr 14 07:55:47 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Thu Apr 16 17:00:19 2026"
      },
      "message": "xfs: add a test for number of open zones on conventional devices\n\nTest that mounts of zoned file systems on conventional devices don\u0027t\ncreate more open zones than allowed when the last blocks in one or more\nzones have been invalidated.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "dde983e4419abd83568e9c9ebb4b576848d48eb7",
      "tree": "56c14b2e6f3bc3f5b4b33e565abcd4f026be566e",
      "parents": [
        "56b35283cf8e98b50c13f64912161830e6bd0a08"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Mon Apr 13 17:50:54 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Thu Apr 16 16:49:53 2026"
      },
      "message": "xfs/841: actually compare the new filesystem contents to the proto dir\n\nWe should confirm that the directory tree was correctly copied into the\nnew filesystem, not just that the image files all have the same\nchecksum.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "56b35283cf8e98b50c13f64912161830e6bd0a08",
      "tree": "5ec33c19ed742293e67a97ee108508c9f2dc4387",
      "parents": [
        "c4e03688706d008211c8bb9faeef8fbab3a45615"
      ],
      "author": {
        "name": "Jan Prusakowski",
        "email": "jprusakowski@google.com",
        "time": "Fri Apr 10 13:18:20 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Thu Apr 16 16:48:18 2026"
      },
      "message": "generic/050: handle f2fs as nojournal filesystem\n\nF2FS uses a checkpoint mechanism for metadata consistency rather than a\ntraditional journal. Roll-forward recovery is only needed if there are\nfsync\u0027d files since the last checkpoint.\n\nIn this test case, files are created without fsync, so there is no\nroll-forward data to replay during mount.\n\nTherefore, F2FS does not need to write to the device to recover, and\nsuccessfully mounts on the read-only block device. Thus, it should be\ntreated as nojournal in this case.\n\nSigned-off-by: Jan Prusakowski \u003cjprusakowski@google.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "c4e03688706d008211c8bb9faeef8fbab3a45615",
      "tree": "e384ccef4714304aeef3d9414fc07c51aab0ed3c",
      "parents": [
        "f3e91c87aa9f1a5a4cea4270d1c22c6ba091f34a"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Thu Apr 09 15:22:27 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Apr 13 19:41:25 2026"
      },
      "message": "generic: test fsync against a removed directory\n\nTest that if we fsync a directory that became empty after removing it\nand we have a power failure, we are able to mount the filesystem and the\ndirectory does not exists anymore.\n\nThis exercises a bug found in btrfs which is fixed by the following patch:\n\n  btrfs: fix missing last_unlink_trans update when removing a directory\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Boris Burkov \u003cboris@bur.io\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "f3e91c87aa9f1a5a4cea4270d1c22c6ba091f34a",
      "tree": "7fe0e6e22b07c09afa24c088c34e50b69af1f8c3",
      "parents": [
        "53e68c2afbb9c62de47a227dd05b4373ff85aa1c"
      ],
      "author": {
        "name": "Ojaswin Mujoo",
        "email": "ojaswin@linux.ibm.com",
        "time": "Fri Apr 10 06:36:06 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Apr 13 17:42:42 2026"
      },
      "message": "treewide: Use _sysfs_queue_path helper in all queue access locations\n\nThe sysfs queue dir for partitions is present in their parent device\u0027s\nsysfs dir. This requires extra checks when trying to reading queue data\nfrom sysfs. Currently, fstests open codes this handling or straight up\nignores it in some places.\n\nAvoid this by converting all remaining direct sysfs queue accesses to\nuse the _sysfs_queue_path helper function. This ensures proper handling\nof partitions across the entire codebase and provides a consistent\ninterface for accessing queue attributes.\n\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "53e68c2afbb9c62de47a227dd05b4373ff85aa1c",
      "tree": "bd7bb5f5367dc1d8e5f9420c7463b37354629590",
      "parents": [
        "fb11f06d9026a9a449c4a5afb7e9263e88fdea22"
      ],
      "author": {
        "name": "Ojaswin Mujoo",
        "email": "ojaswin@linux.ibm.com",
        "time": "Fri Apr 10 06:36:05 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Apr 13 17:42:41 2026"
      },
      "message": "generic/775: Fix an infinite loop due to variable name clash\n\nWe use i as the iteration variable in the main test loop as well as some\ninternal loops. Due to this clash, $i variable of main test loops was\ngetting modified by the following loop in prep_mixed_mapping().\n\n\tfor ((i\u003d0; i\u003cnum_blocks; i++)); do\n\nIf num_blocks is less than 10 (example ext4 with blocksize 4k and\ncluster size 8k) i would always be set as 3 and the main loop would\nnever exit. Use local variable to fix this and while we are at it,\nrename it for clarity.\n\nReported-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "fb11f06d9026a9a449c4a5afb7e9263e88fdea22",
      "tree": "57cdb8d9d17bcba1e793ddadf5d0f72425a14045",
      "parents": [
        "4dc8a079a670c0831e75dd9fc25e02f94b261807"
      ],
      "author": {
        "name": "Ojaswin Mujoo",
        "email": "ojaswin@linux.ibm.com",
        "time": "Fri Apr 10 06:36:04 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Apr 13 17:42:41 2026"
      },
      "message": "generic/765: Ignore mkfs warning\n\nThis test validates atomic writes for all possible block sizes. In ext4, for\nsmaller block sizes with configurations like:\n\nexport MKFS_OPTIONS\u003d\"-O bigalloc,quota -b 65536 -C 131072\"\n\nThe output can get corrupted with warnings like below because clustersize\nmore than 16xbs is experimental:\n\n+ 16 times the block size is considered experimental\n\nHence pipe these to seqres.full to avoid false negatives.\n\nReported-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "4dc8a079a670c0831e75dd9fc25e02f94b261807",
      "tree": "5a8c55ea593089e32f3ccef9aee06fa765e22330",
      "parents": [
        "2c002c3a86c03155e6129fea77c1b2c29a43b18a"
      ],
      "author": {
        "name": "Ojaswin Mujoo",
        "email": "ojaswin@linux.ibm.com",
        "time": "Fri Apr 10 06:36:03 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Apr 13 17:42:41 2026"
      },
      "message": "generic/765: Fix sysfs queue path for nvme partitions\n\nThis tests checks atomic write limits reported by statx() are same as\nthe ones reported by sysfs, however nvme partitions don\u0027t have the\n/sys/block/nvme0n1p1 style entry and also use the namespace\u0027s queue\nlimits for atomic writes. This causes the test to fail because it\nexpects /sys/block/nvme0n*p* to be present.\n\nHence, use the new _sysfs_queue_path() helper to get the correct\natomic write limits\n\nAlso, fix a small typo (s/awu_min/awu_max) when printing awu limits to\nseqres.full\n\nReported-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "2c002c3a86c03155e6129fea77c1b2c29a43b18a",
      "tree": "b3b4e871b9dba098e5ee22c92c05cc30a88fd029",
      "parents": [
        "ea4d04e7b6766118bbf0cbe596de2e41a325119c"
      ],
      "author": {
        "name": "Ojaswin Mujoo",
        "email": "ojaswin@linux.ibm.com",
        "time": "Fri Apr 10 06:36:02 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Apr 13 17:42:41 2026"
      },
      "message": "common/rc: Add _sysfs_queue_path helper with partition support\n\nAdd a generic helper function to get the sysfs queue path for block\ndevices, properly handling partitions. Partitions don\u0027t have their own\nqueue directory in sysfs - they inherit from their parent device.\n\nThis helper checks if a device is a partition and returns the parent\ndevice\u0027s queue path accordingly, making it easier to access queue\nattributes for both whole disks and partitions.\n\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "ea4d04e7b6766118bbf0cbe596de2e41a325119c",
      "tree": "1ba9783efd55dc8bf3456a5b6eabdbf0b165ca13",
      "parents": [
        "0bece2e05be1c5179654f7437519f80eeef71111"
      ],
      "author": {
        "name": "Ojaswin Mujoo",
        "email": "ojaswin@linux.ibm.com",
        "time": "Fri Apr 10 06:36:01 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Apr 13 17:42:41 2026"
      },
      "message": "ext4/061,062: Minor fixes and refactoring\n\nFix 2 issues in the tests:\n\n1. Use fs atomic write limits instead of bdev\u0027s\n\nThe tests use block device\u0027s limits instead of limits advertised\nby filesystem. This can cause failures because block device might\nadvertise a higher maximum than the FS.  Fix the tests to use\nfilesystem\u0027s limits instead.\n\n2. Fix the test loop range\n\nFix the test loop start and end so that our calculations for\nblocksize, clustersize and iosize are correct.\n\nReported-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "0bece2e05be1c5179654f7437519f80eeef71111",
      "tree": "0df84a792d7bde01afa218a40d1ed933ff8d68c9",
      "parents": [
        "29dbf07039172295ebe3ae158eb1a7e44dedcc96"
      ],
      "author": {
        "name": "Disha Goel",
        "email": "disgoel@linux.ibm.com",
        "time": "Mon Mar 23 12:40:05 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Apr 01 15:07:25 2026"
      },
      "message": "generic/730: skip test if DAX mount option is enabled\n\nThe generic/730 test utilizes the scsi_debug driver to create a\nsynthetic SCSI block device. Since scsi_debug does not support\nDAX capabilities, attempting to mount it with \"-o dax\" results\nin failures (specifically on ext4).\n\nSince this test is not DAX-related, exclude it when DAX is\nspecified in MOUNT_OPTIONS to avoid compatibility issues with\nscsi_debug.\n\nSigned-off-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "29dbf07039172295ebe3ae158eb1a7e44dedcc96",
      "tree": "7f33d1cad6394232fdf28851eefc768d6e306eb5",
      "parents": [
        "c34c06b9728c2b3e3dbe7666de29f0fb57f24f33"
      ],
      "author": {
        "name": "Long Li",
        "email": "leo.lilong@huawei.com",
        "time": "Wed Apr 01 06:06:32 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Apr 01 15:07:08 2026"
      },
      "message": "xfs/018: test log attr replay with zero-length attr value\n\nKernel commit d72f2084e309 (\"xfs: fix ri_total validation in\nxlog_recover_attri_commit_pass2\") fixed a bug where setting a\nzero-length attribute value would cause incorrect ri_total\nvalidation during log recovery.\n\nAdd test cases to xfs/018 to cover this scenario across attr\nfork formats: extent and remote.\n\nUsing echo -n \"\" | attr -s is unreliable for empty values since\nattr may treat stdin EOF as no value provided. Instead, handle\nzero-length values explicitly in test_attr_replay() by using\nattr -s -V \"\" when the value is empty.\n\nSigned-off-by: Long Li \u003cleo.lilong@huawei.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "c34c06b9728c2b3e3dbe7666de29f0fb57f24f33",
      "tree": "6b007f35c20e9f1c8e08f3a1c302412b062a564a",
      "parents": [
        "8deafb5c487e73c9384df2fcbab523b12007875b"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Tue Mar 31 14:15:10 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Apr 01 15:07:08 2026"
      },
      "message": "fstests: add kernel commit IDs for patches already merged upstream\n\nSeveral tests mention patches that are already in Linus\u0027 git tree, so add\ntheir commit IDs. For generic/762, also use \"fixed_by_fs_commit xfs\"\ninstead of \"_fixed_by_git_commit kernel\" since it\u0027s a XFS specific commit\nand it does not make sense for the test to report that commit in case it\nfails when running against a filesystem other than XFS.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "8deafb5c487e73c9384df2fcbab523b12007875b",
      "tree": "ae761ea3f3a4475c09d4b02ad11dc122878b4f99",
      "parents": [
        "7a2fe2c2f7be4982cdbbb882e1802966fef448f5"
      ],
      "author": {
        "name": "Hans Holmberg",
        "email": "hans.holmberg@wdc.com",
        "time": "Fri Mar 27 12:34:29 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Apr 01 15:07:08 2026"
      },
      "message": "xfs: test that zone_gc_low_space writes start gc for rw fses\n\nTest that writes to the sysfs attribute zone_gc_low_space triggers\ngarbage collection for rw (but not ro) file systems.\n\nSigned-off-by: Hans Holmberg \u003chans.holmberg@wdc.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "7a2fe2c2f7be4982cdbbb882e1802966fef448f5",
      "tree": "13edbb4063fe58b18a71c3e945bf3ff9de91cab5",
      "parents": [
        "2d614deaed2919f73ff9595fb0cec5ff37201aa9"
      ],
      "author": {
        "name": "Hans Holmberg",
        "email": "hans.holmberg@wdc.com",
        "time": "Fri Mar 27 12:34:28 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Apr 01 15:07:08 2026"
      },
      "message": "xfs/647: turn rt dev block device lookup into a common helper\n\nTurn the logic figuring out on which block device the rt data is stored on\ninto a common helper.\n\nSigned-off-by: Hans Holmberg \u003chans.holmberg@wdc.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "2d614deaed2919f73ff9595fb0cec5ff37201aa9",
      "tree": "323c2625ffeb97bfebb4303781826b294be6e523",
      "parents": [
        "a44a26f93b056bf4408bc4884df111ab05a973f3"
      ],
      "author": {
        "name": "Leo Martins",
        "email": "loemra.dev@gmail.com",
        "time": "Tue Mar 24 19:09:52 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Apr 01 15:07:08 2026"
      },
      "message": "btrfs: fix stale errno check in btrfs_encoded_read/write helpers\n\nThe atoll() error check `if (offset \u003d\u003d 0 \u0026\u0026 errno !\u003d 0)` can falsely\ntrigger because errno is not cleared before the call. Library\ninitialization code (e.g. libcap calling prctl(PR_CAPBSET_READ) which\nfails with EINVAL) can leave errno set to a non-zero value. When the\ncaller passes offset\u003d0 (a valid value), atoll() returns 0 without\nmodifying errno, and the stale errno causes the helper to print usage\nand exit.\n\nThis caused btrfs/333 to fail consistently on systems where libcap is\nlinked, since every call with offset 0 would bail out.\n\nFix by clearing errno before the atoll() calls in both\nbtrfs_encoded_read and btrfs_encoded_write helpers.\n\nSigned-off-by: Leo Martins \u003cloemra.dev@gmail.com\u003e\nReviewed-by: Mark Harmstone \u003cmark@harmstone.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "a44a26f93b056bf4408bc4884df111ab05a973f3",
      "tree": "3f1a2f8deb8bd769413a8222923f2d713598ba50",
      "parents": [
        "39b31fe6e746ada86179ecb698d7f891d633218a"
      ],
      "author": {
        "name": "Leo Martins",
        "email": "loemra.dev@gmail.com",
        "time": "Tue Mar 24 20:40:00 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Apr 01 15:07:08 2026"
      },
      "message": "generic/301: skip extent count check on btrfs\n\nThe 2/3 fragmentation threshold was designed for XFS\u0027s cowextsize\nmechanism and is not applicable to btrfs. After commit 0dc118b3c327\n(\"btrfs: be less aggressive with metadata overcommit when we can do\nfull flushing\"), btrfs commits transactions more frequently during\nwriteback, reducing the extent allocator\u0027s opportunity to coalesce\nadjacent CoW extents. This causes the extent count to sometimes cross\nthe threshold, making the test flaky on btrfs.\n\nSkip only the extent count assertion for btrfs while keeping the CoW\nwrite + remount + md5sum data integrity checks, which remain useful.\n\nSigned-off-by: Leo Martins \u003cloemra.dev@gmail.com\u003e\nReviewed-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "39b31fe6e746ada86179ecb698d7f891d633218a",
      "tree": "e9b5bcc393ab88c5218a77611da291c3c2a1cb45",
      "parents": [
        "271d7a1257f762a4fff2c8cc433b86cc6dd1320b"
      ],
      "author": {
        "name": "Yangyang Zang",
        "email": "zangyangyang66@gmail.com",
        "time": "Thu Mar 19 03:35:19 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 31 19:40:34 2026"
      },
      "message": "f2fs: add testcase to check resize corrupting root inode\n\nThis is a regression test to check whether the f2fs root inode\nis corrupted after the resize operation.\nDuring the resize operation, SSA data blocks are migrated and\nzeroed. This process may incorrectly zero out the main area\nblocks, leading to root inode corruption.\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nCc: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Yangyang Zang \u003czangyangyang1@xiaomi.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "271d7a1257f762a4fff2c8cc433b86cc6dd1320b",
      "tree": "33fb31dc7048728c6dae84bcbcb6517df2197756",
      "parents": [
        "c17136d0c6c4ad6c8fd07561d4f63d5026d59401"
      ],
      "author": {
        "name": "Yangyang Zang",
        "email": "zangyangyang66@gmail.com",
        "time": "Thu Mar 19 03:35:18 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 31 19:40:23 2026"
      },
      "message": "common/config: export F2FS_RESIZE_PROG\n\nexport F2FS_RESIZE_PROG w/ resize.f2fs, it can be used for resize f2fs.\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nCc: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Yangyang Zang \u003czangyangyang1@xiaomi.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "c17136d0c6c4ad6c8fd07561d4f63d5026d59401",
      "tree": "ea80f3eaca6c4636b0d8b72327837c255a5de1ec",
      "parents": [
        "78b8a11f8c2f617f81a35cc58ee83f3ac17cdb56"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Mon Mar 16 23:29:35 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri Mar 20 10:55:43 2026"
      },
      "message": "xfs/805: adjust for new autofsck fsproperty defaults\n\nNow that mkfs will set autofsck\u003drepair for filesystems that have both\nreverse space mappings and file parent pointers enabled, let\u0027s stop\ntesting the \"no autofsck option at all\" scenario to avoid problems with\nolder mkfs.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "78b8a11f8c2f617f81a35cc58ee83f3ac17cdb56",
      "tree": "92706122da181bd72f84a7b976d477a355cdeb4d",
      "parents": [
        "04ee3a4f0d19da31b17d2b8b3d542273af5d3916"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Mon Mar 16 23:29:19 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri Mar 20 10:55:43 2026"
      },
      "message": "xfs/6{59-61}: force xfs_healer to run\n\nSet the autofsck property so that xfs_healer actually runs on\nfilesystems with old feature sets.  Since these tests are looking for\nerror reports that don\u0027t require backref metadata (media errors, file IO\nerrors, shutdowns) we needn\u0027t _notrun them.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "04ee3a4f0d19da31b17d2b8b3d542273af5d3916",
      "tree": "3a9701a17985acf9c56cb2fd8bccde24c6aab662",
      "parents": [
        "57d71a884dd1b3b3c44a27d2d106b3be84ddc5fb"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Mon Mar 16 23:29:03 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri Mar 20 10:55:43 2026"
      },
      "message": "common: ignore stderr for the two new svcname helpers\n\nIf either utility doesn\u0027t support the --svcname switch, ignore the\nerror output and just return an empty string.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "57d71a884dd1b3b3c44a27d2d106b3be84ddc5fb",
      "tree": "e8de2751d9c922077f712df4ecd0118236162099",
      "parents": [
        "aa5b0dcf301dc167cf9c7c57622472ea3ffa958d"
      ],
      "author": {
        "name": "Pankaj Raghav",
        "email": "p.raghav@samsung.com",
        "time": "Thu Mar 12 19:53:08 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:44 2026"
      },
      "message": "ltp: add support for FALLOC_FL_WRITE_ZEROES to fsx and fsstress\n\nAdd FALLOC_FL_WRITE_ZEROES support to both fsx and fsstress.\nFALLOC_FL_WRITE_ZEROES flag was added in the kernel as a part of Zhang\nYi\u0027s series [1].\n\nFALLOC_FL_KEEP_SIZE is not supported when FALLOC_FL_WRITE_ZEROES is\nused.\n\n[1] https://lore.kernel.org/linux-fsdevel/20250619111806.3546162-1-yi.zhang@huaweicloud.com/\n\nSigned-off-by: Pankaj Raghav \u003cp.raghav@samsung.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "aa5b0dcf301dc167cf9c7c57622472ea3ffa958d",
      "tree": "e0607cfdb97798b1cc246b35e6684d879e141811",
      "parents": [
        "de37793e7b07f467d213a04250bbeb83fa41ea5a"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Thu Mar 12 14:21:30 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:44 2026"
      },
      "message": "xfs: test xfs_healer can follow private mntns mount moves\n\nMake sure that when xfs_healer needs to reopen a filesystem to repair\nit, it can still find the filesystem even if it has been mount --move\u0027d.\nThis requires a bunch of private namespace magic.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "de37793e7b07f467d213a04250bbeb83fa41ea5a",
      "tree": "0357a29e00c77e3c71feaa3daa162c6fa692fa0b",
      "parents": [
        "df0f4b76c572b517068a00ac360f9622417c3778"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:53:46 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:44 2026"
      },
      "message": "xfs: test xfs_healer startup service\n\nMake sure that xfs_healer_start can actually start up xfs_healer service\ninstances when a filesystem is mounted.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "df0f4b76c572b517068a00ac360f9622417c3778",
      "tree": "22397e8565013a14c878f5ec766a3322976306f0",
      "parents": [
        "17fdaa0ba3f1e36fec1514f8a511898b13897a86"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:53:31 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:44 2026"
      },
      "message": "xfs: test xfs_healer background service\n\nMake sure that when xfs_healer can monitor and repair filesystems when it\u0027s\nrunning as a systemd service, which is the intended usage model.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "17fdaa0ba3f1e36fec1514f8a511898b13897a86",
      "tree": "9d380cf1685cec1550f4a0cb93af88c33b83a016",
      "parents": [
        "309e54e83e1f64eb79cd557f2ff73dabb01bbb1a"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:53:15 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:44 2026"
      },
      "message": "xfs: test xfs_healer wont repair the wrong filesystem\n\nMake sure that when xfs_healer needs to reopen a filesystem to repair it, it\nwon\u0027t latch on to another xfs filesystem that has been mounted atop the same\nmountpoint.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "309e54e83e1f64eb79cd557f2ff73dabb01bbb1a",
      "tree": "a1636233ef6fb4e7c0a75c052c361c2a2ef1ce65",
      "parents": [
        "20dffed104b65a84377dd5431a9ebaf31eedd7fe"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:52:59 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:44 2026"
      },
      "message": "xfs: test xfs_healer can follow mount moves\n\nMake sure that when xfs_healer needs to reopen a filesystem to repair it,\nit can still find the filesystem even if it has been mount --move\u0027d.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "20dffed104b65a84377dd5431a9ebaf31eedd7fe",
      "tree": "f3e2121058b4907823e51340743eb0f6dc9997ca",
      "parents": [
        "8e5ed6fcef9644fba010f1e9bc82fc88df9519f8"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:52:44 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:44 2026"
      },
      "message": "xfs: test xfs_healer can initiate full filesystem repairs\n\nMake sure that when xfs_healer can\u0027t perform a spot repair, it will actually\nstart up xfs_scrub to perform a full scan and repair.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "8e5ed6fcef9644fba010f1e9bc82fc88df9519f8",
      "tree": "6f69bb226afc7d039ab7a9a86970a0921989725a",
      "parents": [
        "eb1013c4f2698d8fa6ae32e9ce0a9e71e738a630"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:52:28 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:44 2026"
      },
      "message": "xfs: test xfs_healer can report filesystem shutdowns\n\nMake sure that xfs_healer can actually report abnormal filesystem shutdowns.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "eb1013c4f2698d8fa6ae32e9ce0a9e71e738a630",
      "tree": "8ee95e1bfea7665350e5fb57209a16c789d28b3d",
      "parents": [
        "aa3d8defe09a845cc5ecceea05d6b0da2711a09b"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:52:13 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:44 2026"
      },
      "message": "xfs: test xfs_healer can report file media errors\n\nMake sure that xfs_healer can actually report media errors as found by the\nkernel.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "aa3d8defe09a845cc5ecceea05d6b0da2711a09b",
      "tree": "4fc7cd154de9396719b04795376bb2ec59c47cd8",
      "parents": [
        "a951e61b684cfd21afde34a8930fc9666efe68b8"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:51:57 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:43 2026"
      },
      "message": "xfs: test xfs_healer can report file I/O errors\n\nMake sure that xfs_healer can actually report file I/O errors.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "a951e61b684cfd21afde34a8930fc9666efe68b8",
      "tree": "3964e05e3b1d805cf42dce961aad61db8d24c274",
      "parents": [
        "e76e776e4310b481ce4221613f33a59b3efd5ff5"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:51:41 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:43 2026"
      },
      "message": "xfs: test xfs_healer can fix a filesystem\n\nMake sure that xfs_healer can actually fix an injected metadata corruption.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "e76e776e4310b481ce4221613f33a59b3efd5ff5",
      "tree": "eace1fca1eec167e45707e2bdfa688cce8cff1d3",
      "parents": [
        "15548b5e84828c8b8a0f3aca675039ac3e245ed7"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:51:26 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:43 2026"
      },
      "message": "xfs: test xfs_healer\u0027s event handling\n\nMake sure that xfs_healer can handle every type of event that the kernel\ncan throw at it by initiating a full scrub of a test filesystem.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "15548b5e84828c8b8a0f3aca675039ac3e245ed7",
      "tree": "74ac4c814bb13a29f85dd5ded1aafc0340c31a91",
      "parents": [
        "1eef51a44b3f6c71916a38335fb283d96faab3a8"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:51:10 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:43 2026"
      },
      "message": "xfs: set up common code for testing xfs_healer\n\nAdd a bunch of common code so that we can test the xfs_healer daemon.\nMost of the changes here are to make it easier to manage the systemd\nservice units for xfs_healer and xfs_scrub.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "1eef51a44b3f6c71916a38335fb283d96faab3a8",
      "tree": "443ff53ac19a506f7aa5dcab438e72143ef32641",
      "parents": [
        "c90d3c12ffe181ff30afa1e5d2c587458da09a6f"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:50:55 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:43 2026"
      },
      "message": "xfs: test io error reporting via healthmon\n\nCreate a new test to make sure the kernel can report IO errors via\nhealth monitoring.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "c90d3c12ffe181ff30afa1e5d2c587458da09a6f",
      "tree": "feaeafbbedf980e52660fa1c3581d9a26162f3ce",
      "parents": [
        "79f6b1c3e4d8e5e859c63779af82d57c40222dfc"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:50:39 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:43 2026"
      },
      "message": "xfs: test for metadata corruption error reporting via healthmon\n\nCheck if we can detect runtime metadata corruptions via the health\nmonitor.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "79f6b1c3e4d8e5e859c63779af82d57c40222dfc",
      "tree": "123a664bfa78f8a15eef24eac6ff6e6fb03422de",
      "parents": [
        "29d120e41c3d3d08b8eebe0d393cb79ef59589cc"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:50:23 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:43 2026"
      },
      "message": "xfs: test health monitoring code\n\nAdd some functionality tests for the new health monitoring code.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "29d120e41c3d3d08b8eebe0d393cb79ef59589cc",
      "tree": "f3a5d99919dd74f52cf87ce9348d7e7e02b4cff9",
      "parents": [
        "fd92924495149d3e6e3447ab85f50427c47e3a86"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Tue Mar 10 03:50:08 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Tue Mar 17 03:31:43 2026"
      },
      "message": "generic: test fsnotify filesystem error reporting\n\nUse dmerror to inject a media error for a file\u0027s storage, then run\nsome IO and make sure that fanotify reports the IO errors.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "fd92924495149d3e6e3447ab85f50427c47e3a86",
      "tree": "670834fa7bcb2f17115602b3a0ae0eac239773a8",
      "parents": [
        "66c672a2e84561353e93b7d096d5f78d2df98549"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Wed Mar 11 04:14:43 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat Mar 14 20:02:00 2026"
      },
      "message": "xfs/62[3-8]: require XFS_SCRUB_PROG\n\nQA reports that xfs/62[3-8] fail because they didn\u0027t install\nxfsprogs-xfs_scrub package and this test requires xfs_scrub(8).\nAdd the missing _require call, and update the README so that anyone\nrunning fstests on RHEL/Fedora actually get all the necessary\ncomponents to do a full test of XFS.\n\nCc: fstests@vger.kernel.org # v2024.06.27\nFixes: 4de8fd7860a2bb (\"scrub: test correction of directory tree corruptions\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "66c672a2e84561353e93b7d096d5f78d2df98549",
      "tree": "e1766907e88fa5d7037fbcf44f855606a97567ed",
      "parents": [
        "c6946bc36b9f73891e2e438cb1362ae09da3550e"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Thu Feb 26 14:34:37 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat Mar 14 20:02:00 2026"
      },
      "message": "btrfs: test create a bunch of files with name hash collision\n\nTest that if we create a high number of files with a name that results in\na hash collision, the filesystem is not turned to RO due to a transaction\nabort. This could be exploited by malicious users to disrupt a system.\n\nThis exercies a bug fixed by the following kernel patch:\n\n \"btrfs: fix transaction abort on file creation due to name hash collision\"\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Boris Burkov \u003cboris@bur.io\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "c6946bc36b9f73891e2e438cb1362ae09da3550e",
      "tree": "2a8b37d69dfbe563038b93e3c35f351970cdeb8d",
      "parents": [
        "aad362549a8a9514335b4f266c7e68c3741c89a5"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Thu Feb 26 14:34:24 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat Mar 14 20:02:00 2026"
      },
      "message": "btrfs: test creating a large number of snapshots of a received subvolume\n\nTest that we can create a large number of snapshots of a received\nsubvolume without triggering a transaction abort due to leaf item\noverflow. Also check that we are able to delete the snapshots and use\nthe last one for an incremental send/receive despite an item overflow\nwhen updating the uuid tree to insert a BTRFS_UUID_KEY_RECEIVED_SUBVOL\nitem.\n\nThis exercises a bug fixed by the following kernel patch:\n\n  \"btrfs: fix transaction abort when snapshotting received subvolumes\"\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Boris Burkov \u003cboris@bur.io\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "aad362549a8a9514335b4f266c7e68c3741c89a5",
      "tree": "397c4a1655faf958062677456eaca9694a592bd4",
      "parents": [
        "8ca8c3c238bcce78a291d73372e4669b5d0bd382"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Fri Feb 27 00:12:05 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat Mar 14 20:02:00 2026"
      },
      "message": "btrfs: test setting the same received UUID to a lot of subvolumes\n\nTest that using the received subvol ioctl to set a received UUID on a root\ndoes not trigger a transaction abort (and turn the filesystem to RO mode)\nif a user abuses by assigning the same received UUID to a large number of\nsubvolumes.\n\nThis exercises a bug fixed by the following kernel patch:\n\n \"btrfs: fix transaction abort on set received ioctl due to item overflow\"\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "8ca8c3c238bcce78a291d73372e4669b5d0bd382",
      "tree": "da0556382f7ae8e5952b236841e159c5e1a8c805",
      "parents": [
        "02e625a5875ae42ba63ca2622bf2be7759a1f8ad"
      ],
      "author": {
        "name": "Johannes Thumshirn",
        "email": "johannes.thumshirn@wdc.com",
        "time": "Wed Feb 25 10:27:41 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat Mar 14 20:02:00 2026"
      },
      "message": "fstests: use _fixed_by_fs_commit where appropriate\n\nUse the newly introduced _fixed_by_fs_commit function where appropriate.\n\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "02e625a5875ae42ba63ca2622bf2be7759a1f8ad",
      "tree": "75ed5b470b6f7b9bd71a857e62beebd7b7cf893f",
      "parents": [
        "01d24d6b0b286b666cabc4c4790f3049f3a34ebe"
      ],
      "author": {
        "name": "Johannes Thumshirn",
        "email": "johannes.thumshirn@wdc.com",
        "time": "Wed Feb 25 10:27:40 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Mar 04 15:58:03 2026"
      },
      "message": "fstests: add _fixed_by_fs_commit helper\n\nAdd a new helper `_fixed_by_fs_commit` eliminating the\n if [ $FSTYP \u003d fs ] \u0026\u0026 _fixed_by_kernel_commit XXXX YYYY\npattern.\n\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "01d24d6b0b286b666cabc4c4790f3049f3a34ebe",
      "tree": "570d44e90a3820c4fe838a8ecd9a9819ccf0ff2b",
      "parents": [
        "3ded3e13c008326d197d11ac975049ed1f8ec922"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Tue Mar 03 18:07:33 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Mar 04 15:58:03 2026"
      },
      "message": "generic: test a directory fsync scenaro after replacing a subdir with a file\n\nTest a scenario where we remove a directory previously persisted, create\na file with the same name and parent directory, create two directories in\nthe same parent directory, create a hard link for the new file in one of\nthe new directories, fsync the directory with the hard link and fsync the\nparent directory. After a power failure we expect both directories to be\npersisted as well as the new file and its hard link.\n\nThis exercises a bug on btrfs fixed by the following kernel patch:\n\n  \"btrfs: log new dentries when logging parent dir of a conflicting inode\"\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "3ded3e13c008326d197d11ac975049ed1f8ec922",
      "tree": "189cf5d513954fb2a73394d59f4272459de4a9d2",
      "parents": [
        "6fe19be2ecc16dd610f1252c849d1c2493325fb2"
      ],
      "author": {
        "name": "Jan Kara",
        "email": "jack@suse.cz",
        "time": "Fri Feb 20 20:33:08 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sat Feb 21 16:28:09 2026"
      },
      "message": "tests: Fix failure in nojournal mode\n\nSeveral tests use fs shutdown. Without journalling the filesystem isn\u0027t\nguaranteed to be consistent after shutdown. So for tests that don\u0027t make\nsure data makes it to the disk using fsync/sync we cannot really test\nmuch. Skip such tests without journalling.\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "6fe19be2ecc16dd610f1252c849d1c2493325fb2",
      "tree": "9ca659cc6c2c430acefdd0e0929352883215b929",
      "parents": [
        "75bbf15c562942d9329fb44ea3b6190509c8f748"
      ],
      "author": {
        "name": "Andrey Albershteyn",
        "email": "aalbersh@kernel.org",
        "time": "Thu Feb 19 15:25:22 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri Feb 20 17:06:47 2026"
      },
      "message": "generic/579: handle quoted cmp output\n\ndiffutils updated cmp with more consistent quoting in commit:\n\n\t69ae797392bd cmp,diff,diff3,sdiff: quote more consistently\n\nThis causes generic/579 to fail from time to time due to grep not\ncatching these errors. Remove quote to work with new and old version of\ncmp.\n\nSigned-off-by: Andrey Albershteyn \u003caalbersh@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "75bbf15c562942d9329fb44ea3b6190509c8f748",
      "tree": "171a2e899c42a7d7c1331d70e8737fe0fa89cbd3",
      "parents": [
        "c26276f53d58477010364a8b1b0fd209a6c943f1"
      ],
      "author": {
        "name": "Filipe Manana",
        "email": "fdmanana@suse.com",
        "time": "Tue Feb 17 18:33:30 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Fri Feb 20 15:51:43 2026"
      },
      "message": "generic: test fsync of a file truncated to a length of zero\n\nTest that if we truncate a file to 0, fsync it, add a hard link to the\nfile and then fsync the parent directory, after a power failure the file\nhas a size of 0 (and the hardlink exists too).\n\nThis exercises a bug fixed by the following kernel patch for btrfs:\n\n  \"btrfs: fix zero size inode with non-zero size after log replay\"\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "c26276f53d58477010364a8b1b0fd209a6c943f1",
      "tree": "899f78aecb79fcbb813040195c7c6c5e6f512927",
      "parents": [
        "eeb894a242c8d200b7ed4c8b7da3d54e24e02c6f"
      ],
      "author": {
        "name": "Qu Wenruo",
        "email": "wqu@suse.com",
        "time": "Mon Feb 16 21:29:24 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Wed Feb 18 07:25:59 2026"
      },
      "message": "fstests: btrfs: add a test case for failed compressed inline attempt\n\n[BUG]\nThere is a long existing behavior that if a compressed inline attempt\nfailed, the whole inode is marked incompressible.\n\nFurthermore, the default threshold for compressed inline implies a\npretty high compression ratio (2K max inline vs 4K block size, thus 50%\ncompression ratio).\n\nThis makes btrfs to mark inodes incompressible prematurely.\n\n[TEST]\nThe new test case is based on the previous btrfs/343 one, which will do:\n\n- Create and mount the fs with compress,max_inline\u003d4\n  4 bytes will be too small for any header, thus all compressed inline\n  writes should fail.\n\n- Do the following operations:\n  * Buffered write [0, blocksize / 2)\n    Which can be inlined if using the default max_inline mount option\n    and 4K fs block.\n    But the new max_inline\u003d4 will reject such compressed inline attempt.\n\n    And such one block write should not trigger compression thus no\n    compression ratio based check.\n\n  * Sync\n    For unpatched kernels, this will set the inode with NOCOMPRESS flag\n    and reject all future compression on that inode.\n\n  * Buffered write [1M, 2M)\n    For unpatched kernels, the range will not be compressed due to the\n    NOCOMPRESS flag.\n\n- Unmount the fs\n\n- Maker sure that:\n  * The inode has no NOCOMPRESS flag\n  * File extent at file offset 1M is being compressed\n\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "eeb894a242c8d200b7ed4c8b7da3d54e24e02c6f",
      "tree": "2bba06d8a4727325e4ddfc07efbafd4f9318d5cd",
      "parents": [
        "66c8f2df3f3a8803c05336fff4c3ae3048b468b1"
      ],
      "author": {
        "name": "Qu Wenruo",
        "email": "wqu@suse.com",
        "time": "Mon Feb 09 09:57:35 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Feb 16 13:17:52 2026"
      },
      "message": "fstests: btrfs: add a regression test for incorrect inode incompressible flag\n\n[BUG]\nSince kernel commit 59615e2c1f63 (\"btrfs: reject single block sized\ncompression early\"), a single block write at file offset 0, which can\nnot be inlined due the inode size, will mark the inode incompressible.\n\n[REGRESSION TEST]\nThe new regression test will do:\n\n- Create and mount the fs with compression,max_inline\u003d2k\n\n- Do the following operations:\n  * Truncate the inode to 2 * blocksize\n    This will rule out any future inlined writes.\n\n  * Buffered write [0, 2K)\n    Which will not be inlined.\n\n  * Sync\n    For affected kernels, this will set the inode with NOCOMPRESS\n    and reject all future compression on that inode.\n\n  * Buffered write [1M, 2M)\n    For affected kernels, the range will not be compressed due\n    to the NOCOMPRESS flag.\n\n- Unmount the fs\n\n- Make sure that:\n  * The inode has no NOCOMPRESS flag\n  * File extent at file offset 1M is being compressed\n\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "66c8f2df3f3a8803c05336fff4c3ae3048b468b1",
      "tree": "d035aa094b5ab8b7061cccbc4f45624ea3817e33",
      "parents": [
        "d290a3c1b673bdb9904681c06364f678702bcd9c"
      ],
      "author": {
        "name": "Joanne Chang",
        "email": "joannechien@google.com",
        "time": "Thu Jan 08 02:25:01 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Mon Feb 09 03:56:05 2026"
      },
      "message": "common/rc: add _require_max_file_range_blocks helper\n\ngeneric/735 attempts to create a file with nearly 2^32 blocks. However,\nsome filesystems have a maximum file block limit below this threshold.\nFor instance, F2FS is limited to approximately 2^30 blocks due to the\ncapacity of the inode. So add _require_blocks_in_file helper to skip the\ntest in such cases.\n\nThe helper uses a hardcoded constant instead of a programmatic method,\nso that bugs which affect the maximum file size are not masked.\n\nSigned-off-by: Joanne Chang \u003cjoannechien@google.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "d290a3c1b673bdb9904681c06364f678702bcd9c",
      "tree": "f371c15c455bc06a4faf721b0357a743942c34c0",
      "parents": [
        "08989d57ae35221d68d0835de6cadd7603b5e1dd"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Mon Feb 02 19:11:44 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sun Feb 08 17:36:00 2026"
      },
      "message": "generic/749: don\u0027t write a ton of _mread output to seqres.full\n\nSomething went wrong with this test when testing with fuse4fs, but I\ncouldn\u0027t tell what because this test writes so much data to seqres.full\nthat it completely filled the log partition.  Most of that output was\nfrom checks that actually succeeded, so let\u0027s reduce the amount of\nlogging from _mread (which passes -v) by writing to a tempfile and only\ndumping the output to the .full file if something breaks.\n\nCc: fstests@vger.kernel.org # v2024.06.27\nFixes: e4a6b119e52295 (\"fstests: add mmap page boundary tests\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Carlos Maiolino \u003ccmaiolino@redhat.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    },
    {
      "commit": "08989d57ae35221d68d0835de6cadd7603b5e1dd",
      "tree": "2f86e741d476f3f6b61c4f2d1728e1171118252f",
      "parents": [
        "98dd6070d7eb5b037501345a1da5503daaab1697"
      ],
      "author": {
        "name": "Darrick J. Wong",
        "email": "djwong@kernel.org",
        "time": "Mon Feb 02 19:11:28 2026"
      },
      "committer": {
        "name": "Zorro Lang",
        "email": "zlang@kernel.org",
        "time": "Sun Feb 08 17:31:41 2026"
      },
      "message": "xfs/620: force xattr leaf format for this test\n\nNow that the kernel\u0027s parent pointer update code skips the attr intent\nmechanism when the attr fork is in local/shortform format, we need to\nbloat the attr fork to force the slow path for error injection testing.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Carlos Maiolino \u003ccmaiolino@redhat.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n"
    }
  ],
  "next": "98dd6070d7eb5b037501345a1da5503daaab1697"
}