)]}' { "log": [ { "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" }, { "commit": "98dd6070d7eb5b037501345a1da5503daaab1697", "tree": "8678e43e266e8aeaa24beac1e47257c5caefb50c", "parents": [ "163dbbfaacf0b6d1c62e9363546356e198644f45" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Fri Feb 06 21:54:00 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Feb 08 17:30:04 2026" }, "message": "xfs/018: remove inline xattr recovery tests\n\nIn Linux 7.0 we\u0027ve changed the extended attribute update code to try to\ntake a shortcut for performance reasons. Before walking through the\nattr intent state machine (slow), the update will check to see if the\nattr structure is in short format and will stay in that format after the\nchange. If so, then the incore inode can be updated and logged, and\nthe update is complete (fast) in a single transaction.\n\n(Obviously, for complex attr structures or large changes we still walk\nthrough the intent machinery.)\n\nHowever, xfs/018 tests the behavior of the \"larp\" error injector, which\nonly triggers from inside the attr intent state machine. Therefore, the\nshort format tests don\u0027t actually trip the injector. It makes no sense\nto add a new larp injection callsite for the shortcut because either the\nsingle transaction gets written to disk or it doesn\u0027t.\n\nThe golden output no longer matches because the attr update doesn\u0027t\nreturn EIO and shut down the filesystem due to the larp injection.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Carlos Maiolino \u003ccmaiolino@redhat.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "163dbbfaacf0b6d1c62e9363546356e198644f45", "tree": "972c2f677856fa3b8907104b32404fc247bde6af", "parents": [ "1ec21c2911f39b4aa3bb21d5560f1b6da72b0b5e" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Mon Feb 02 08:57:01 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Tue Feb 03 08:29:50 2026" }, "message": "xfs/841: create a block device that must exist\n\nThis test currently creates a block device node for /dev/ram0,\nwhich isn\u0027t guaranteed to exist, and can thus cause the test to\nfail with:\n\nmkfs.xfs: cannot open $TEST_DIR/proto/blockdev: No such device or address\n\nInstead, create a node for the backing device for $TEST_DIR, which must\nexist.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Luca Di Maio \u003cluca.dimaio1@gmail.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "1ec21c2911f39b4aa3bb21d5560f1b6da72b0b5e", "tree": "6976e73efab0de2709f8a574a262ddfa551cdff5", "parents": [ "6cc08eb813281bc42636fa806830811e8dfcfd41" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Mon Jan 26 13:08:43 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jan 29 16:17:11 2026" }, "message": "generic: test that truncate(2) on fsverity is blocked\n\ntruncate(2) doesn\u0027t go through open and needs special code to block\nit on fsverity files. btrfs was missing this check.\n\nNote that truncate(2) in current core utils uses openat and ftruncate,\nso add our own little test program for it.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "6cc08eb813281bc42636fa806830811e8dfcfd41", "tree": "321a8ac47545d1dca7874f6f437b249f04c3513e", "parents": [ "69cd20bd0498f8d112623be88ce855c063091f19" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Tue Jan 27 15:01:52 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jan 29 16:16:14 2026" }, "message": "generic: add missing kernel commit IDs to tests 784 and 785\n\nThe respective kernel patches are already in Linus\u0027 tree (landed in\nv6.19-rc2), so update the tests to include the commit IDs.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: David Sterba \u003cdsterba@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "69cd20bd0498f8d112623be88ce855c063091f19", "tree": "225908891a85d40ec22306b039242608a1a31c65", "parents": [ "31f7192f90a89a6f808a37c3a3cd30491bd50eba" ], "author": { "name": "Luca Di Maio", "email": "luca.dimaio1@gmail.com", "time": "Thu Jan 08 14:22:22 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 25 16:06:09 2026" }, "message": "xfs: test reproducible builds\n\nWith the addition of the `-p` populate option, SOURCE_DATE_EPOCH and\nDETERMINISTIC_SEED support, it is possible to create fully reproducible\npre-populated filesystems. We should test them here.\n\n[zlang: use _run_fsstress]\n\nSigned-off-by: Luca Di Maio \u003cluca.dimaio1@gmail.com\u003e\nReviewed-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": "31f7192f90a89a6f808a37c3a3cd30491bd50eba", "tree": "a71aa1de9a07b13d9ace4bdcaef4930c0aa8c273", "parents": [ "096adc20b3df8f983727f3130c8cd9fd4fd221a6" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed Jan 21 01:26:21 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 25 16:05:29 2026" }, "message": "misc: allow zero duration for fsstress and fsx\n\nOccasionally the common/fuzzy fuzz test helpers manage to time\nsomething just right such that fsx or fsstress get invoked with a zero\nsecond duration. It\u0027s harmless to exit immediately without doing\nanything, so allow this corner case.\n\n[zlang: No action is taken if duration is 0]\n\nCc: fstests@vger.kernel.org # v2023.05.01\nFixes: 3e85dd4fe4236d (\"misc: add duration for long soak tests\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "096adc20b3df8f983727f3130c8cd9fd4fd221a6", "tree": "76f9b8503d2f99db718ce5200f0c008541a79380", "parents": [ "754368070ac5e548de9ad331bd686b61fa98e437" ], "author": { "name": "Jaegeuk Kim", "email": "jaegeuk@kernel.org", "time": "Fri Jan 23 03:27:44 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 25 16:05:29 2026" }, "message": "f2fs/015: Test correct mkfs options for error cases\n\nLet\u0027s add the required mkfs options for quota mount option cases with\nwrong results.\n\nSigned-off-by: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nCo-developed-by: Joanne Chang \u003cjoannechien@google.com\u003e\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": "754368070ac5e548de9ad331bd686b61fa98e437", "tree": "84433c1eb30f01b125fcb453a6f7ce37738f0f8c", "parents": [ "42c2ccaf370065c15d2f26e99f502a62c1a7c7f7" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed Jan 21 01:27:00 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 25 16:05:29 2026" }, "message": "xfs/614: fix test for parent pointers\n\nAlmost a decade ago, the initial rmap/reflink patches were merged with\nhugely overestimated log space reservations. Although we adjusted the\nactual runtime reservations a few years ago, we left the minimum log\nsize calculations in place to avoid compatibility problems between newer\nmkfs and older kernels.\n\nWith the introduction of parent pointers, we can finally use the more\naccurate reservations for minlog computations and mkfs can format\nsmaller logs as a result. This causes the output of this test to\nchange, though it wasn\u0027t needed until parent pointers were enabled by\ndefault.\n\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": "42c2ccaf370065c15d2f26e99f502a62c1a7c7f7", "tree": "3cb706d210be8f855ae83c1174f63d61d200722b", "parents": [ "725b08a6d61ad5f860198f8c67e09d34b9563954" ], "author": { "name": "caokewu", "email": "caokewu1@uniontech.com", "time": "Mon Jan 19 05:54:11 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 25 16:05:29 2026" }, "message": "ext4/307: allocate donor file size dynamically\n\nCurrently, the donor file size is hardcoded to 250M. fsstress can generate\nmore data than this limit, which causes the `e4compact` helper to crash.\nSpecifically, `e4compact.c:do_defrag_range()` contains the following\nassertion:\n\n assert(donor-\u003elength \u003e\u003d len);\n\nIf the donor file is not large enough to accommodate the data being compacted,\nthis assertion fails (or validation logic rejects it), causing the test to\nfail unexpectedly with an abort or error.\n\nAdditionally, the previous \u0027usage\u0027 calculation used `du -sch`, which outputs\nhuman-readable sizes (e.g., \"1.5M\"). xfs_io\u0027s falloc command does not\nsupport decimal values in length arguments, leading to syntax errors during\nfile allocation.\n\nFix this by:\n1. Using `du -sm` to calcuate the required size in integer MB (rounding up),\n avoiding decimal issues.\n2. Allocating the donor file using this calculated `usage` size instead of\n the fixed 250M limit, ensuring it is always large enough for the operation.\n\nSigned-off-by: caokewu \u003ccaokewu1@uniontech.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "725b08a6d61ad5f860198f8c67e09d34b9563954", "tree": "8aa3a83f69970945a7f47ceb486e0f5b616a1e61", "parents": [ "bc74aaf6859c097439530505dc25fc06dce77c9a" ], "author": { "name": "Nirjhar Roy (IBM)", "email": "nirjhar.roy.lists@gmail.com", "time": "Tue Sep 16 15:30:09 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 25 16:05:29 2026" }, "message": "generic/371: Fix the test to be compatible block sizes upto 64k\n\nWhen this test was ran with btrfs with 64k sector/block size, it\nfailed with\n\n QA output created by 371\n Silence is golden\n +fallocate: No space left on device\n +pwrite: No space left on device\n +fallocate: No space left on device\n +pwrite: No space left on device\n +pwrite: No space left on device\n ...\n\nThis is what is going on:\n\nLet us see the following set of operations:\n --- With 4k sector size ---\n$ mkfs.btrfs -f -b 256m -s 4k -n 4k /dev/loop0\n$ mount /dev/loop0 /mnt1/scratch/\n$ df -h /dev/loop0\nFilesystem Size Used Avail Use% Mounted on\n/dev/loop0 256M 1.5M 175M 1% /mnt1/scratch\n\n$ xfs_io -f -c \"pwrite 0 80M\" /mnt1/scratch/t1\nwrote 83886080/83886080 bytes at offset 0\n80 MiB, 20480 ops; 0.4378 sec (182.693 MiB/sec and 46769.3095 ops/sec)\n\n$ df -h /dev/loop0\nFilesystem Size Used Avail Use% Mounted on\n/dev/loop0 256M 1.5M 175M 1% /mnt1/scratch\n\n$ sync\n$ df -h /dev/loop0\nFilesystem Size Used Avail Use% Mounted on\n/dev/loop0 256M 82M 95M 47% /mnt1/scratch\n\n$ xfs_io -f -c \"pwrite 0 80M\" /mnt1/scratch/t2\nwrote 83886080/83886080 bytes at offset 0\n80 MiB, 20480 ops; 0:00:01.25 (63.881 MiB/sec and 16353.4648 ops/sec)\n\n$ df -h /dev/loop0\nFilesystem Size Used Avail Use% Mounted on\n/dev/loop0 256M 137M 40M 78% /mnt1/scratch\n\n$ sync\n$ df -h /dev/loop0\nFilesystem Size Used Avail Use% Mounted on\n/dev/loop0 256M 162M 15M 92% /mnt1/scratch\n\nNow let us repeat with 64k sector size\n --- With 64k sector size ---\n$ mkfs.btrfs -f -b 256m -s 64k -n 64k /dev/loop0\n$ mount /dev/loop0 /mnt1/scratch/\n$ df -h /dev/loop0\nFilesystem Size Used Avail Use% Mounted on\n/dev/loop0 256M 24M 175M 12% /mnt1/scratch\n\n$ xfs_io -f -c \"pwrite 0 80M\" /mnt1/scratch/t1\nwrote 83886080/83886080 bytes at offset 0\n80 MiB, 20480 ops; 0.8460 sec (94.553 MiB/sec and 24205.4914 ops/sec)\n$\n$ df -h /dev/loop0\nFilesystem Size Used Avail Use% Mounted on\n/dev/loop0 256M 24M 175M 12% /mnt1/scratch\n\n$ sync\n$ df -h /dev/loop0\nFilesystem Size Used Avail Use% Mounted on\n/dev/loop0 256M 104M 95M 53% /mnt1/scratch\n\n$ xfs_io -f -c \"pwrite 0 80M\" /mnt1/scratch/t2\npwrite: No space left on device\n\nNow, we can see that with 64k node size, 256M is not sufficient\nto hold 2 files worth 80M. For 64k, we can also see that the initial\nspace usage on a fresh filesystem is 24M and for 4k its 1.5M. So\nbecause of higher node size, more metadata space is getting used.\nThis test requires the size of the filesystem to be at least capable\nto hold 2 80M files.\nFix this by increasing the fs size from 256M to 330M.\n\nReported-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nSigned-off-by: Nirjhar Roy (IBM) \u003cnirjhar.roy.lists@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "bc74aaf6859c097439530505dc25fc06dce77c9a", "tree": "8bb355986c0a389e6e91c1181d4bf007a120ff64", "parents": [ "8d2e1bd3d2947689921c9496b3aebb3f2a09851c" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Thu Dec 25 22:15:53 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 25 16:05:29 2026" }, "message": "fstests: btrfs: add a new test case that is future-proof\n\nBtrfs\u0027 v1 space cache is marked deprecated since commit 1e7bec1f7d65\n(\"btrfs: emit a warning about space cache v1 being deprecated\"), and\nsoon the v1 space cache mount option will be fully dropped.\n\nFurthermore existing features like block-group-tree, zoned, and bs !\u003d ps\nsupport are all rejecting v1 space cache or forcing the switch to v2\nspace cache.\n\nThe existing btrfs/131 is not going to handle the future well, and that\ntest case is mostly for LTS kernel testing now.\n\nAdd a new test case that is completely v1 cache free, so that it will\nsupport the future where v1 cache is completely dropped, meanwhile still\nkeep the coverage for v2 cache and nospace_cache mount options.\n\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": "8d2e1bd3d2947689921c9496b3aebb3f2a09851c", "tree": "bc063bb820a3538dfdf6275124ba05a28d5d2ef8", "parents": [ "facf3325d90dd6b650983b2cae2369c837d92bf8" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Thu Dec 25 22:15:52 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 25 16:05:29 2026" }, "message": "fstests: btrfs/131: add explicit v1 space cache requirement\n\nThe test case is utilizing v1 space cache, meanwhile v1 space cache\nis already marked deprecated for a while since kernel commit\n1e7bec1f7d65 (\"btrfs: emit a warning about space cache v1 being\ndeprecated\").\n\nFurthermore quite some features are not compatible with v1 cache,\nincluding the soon-to-be-default block-group-tree, and hardware\ndependent zoned features.\n\nCurrently we reject those features for btrfs/131, but what we really\nwant is to only run the test case for supported features/kernels.\nThe current way to reject will not handle future kernels that completely\nrejects v1 space cache.\n\nAdd a new helper, _require_btrfs_v1_cache() to do the check, which\nchecks the following criteria:\n\n- \"space_cache\u003dv1\" mount option is supported\n And to handle default v2 cache behavior, also add \"clear_cache\".\n If the kernel has completely dropped v1 cache support, such mount\n should fail.\n\n- Check if FREE_SPACE_TREE feature exists after above mount\n For bs !\u003d ps cases, v2 cache is enforced to replace v1 cache, thus\n we need to double check to make sure above mount didn\u0027t result v2\n cache.\n\n- Check if cache generation is correct\n If v1 cache is working, the cache_generation should be some valid\n value other than 0 nor (u64)-1.\n\nAnd replace the existing checks on zoned and block-group-tree with the\nnew one.\n\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": "facf3325d90dd6b650983b2cae2369c837d92bf8", "tree": "a2c0c0109ff2d03b72f9e8e2734b505865351089", "parents": [ "a4dbdc5486b43294f73c44f62cc355cc3ed2458e" ], "author": { "name": "Viacheslav Dubeyko", "email": "slava@dubeyko.com", "time": "Tue Jan 06 23:35:56 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 25 16:05:29 2026" }, "message": "xfstests: hfs/hfsplus don\u0027t support metadata journaling\n\nHFS file system doesn\u0027t support metadata journaling.\nThis patch marks HFS file system as not supporting\nmetadata journaling in _has_metadata_journaling()\nof common/rc.\n\nTechnically speaking, HFS+ is journaling file system.\nHowever, current Linux kernel implementation doesn\u0027t\nsupport even journal replay. This patch marks HFS+ file\nsystem as not supporting metadata journaling in\n_has_metadata_journaling() of common/rc. If journaling\nsupport functionality in HFS+ will be implemented,\nthen HFS+ could be deleted from _has_metadata_journaling()\nin the future.\n\nSigned-off-by: Viacheslav Dubeyko \u003cslava@dubeyko.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "a4dbdc5486b43294f73c44f62cc355cc3ed2458e", "tree": "259ff78385dcd70af4e9f9c8ad911f3b1d63baac", "parents": [ "e0ded76267f99ecfeb3e27696489df98d75d7209" ], "author": { "name": "Ojaswin Mujoo", "email": "ojaswin@linux.ibm.com", "time": "Wed Jan 07 10:37:44 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 18 17:23:25 2026" }, "message": "generic/108: fix test hand upon failure to create LV\n\nIn case the lvcreate operation fails, we don\u0027t catch the error and\nproceed as usual. The test then tries to wait for the LV to come up\nbut it never does, causing a hang.\n\nTo fix this:\n1. Add a check to ensure SCSI_DEBUG dev is of required size\n2. Additionally, fail if there are errors while creating the LV.\n\nContext for completeness:\n\nThis was noticed when we accidentally used CONFIG_SCSI_DEBUG\u003dy instead\nof \u003dm, causing it to create an 8MB SCSI debug device. This led to the\nlvcreate operation to fail with:\n\n Insufficient suitable allocatable extents for logical volume lv_108: 68 more required\n\nHowever the test never caught this resulting in a hang.\n\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReported-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nTested-by: Disha Goel \u003cdisgoel@linux.ibm.com\u003e\nReviewed-by: Christoph Hellwig \u003chch@lst.de\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": "e0ded76267f99ecfeb3e27696489df98d75d7209", "tree": "24002060a25db99c8b372b9cb1809e5d8971b154", "parents": [ "8dad086a47019bf46a5b559efb382525324b9254" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Mon Jan 12 13:44:09 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Sun Jan 18 17:18:57 2026" }, "message": "fsx: add missing -T option to getopt_long()\n\nCurrently fsx fails with an invalid argument error when we pass the -T\noption (do not use dontcache IO) to it because it\u0027s not listed in the\ngepopt_long() call.\n\nFix this and add T to the getopt_long() call.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-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": "8dad086a47019bf46a5b559efb382525324b9254", "tree": "568e885a4a9982565718c1161c83900c22e44ceb", "parents": [ "63a29724a85f1999e49bf0a9bf0d22643b6116e5" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Tue Jan 06 12:59:05 2026" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Tue Jan 06 13:21:13 2026" }, "message": "btrfs: test power failure after fsync and rename exchanging directories\n\nTest renaming one directory over another one that has a subvolume inside\nit and fsync a file in the other directory that was previously renamed.\nWe want to verify that after a power failure we are able to mount the\nfilesystem and it has the correct content (all renames visible).\n\nThis exercises a bug fixed by the following kernel commit:\n\n 7ba0b6461bc4 (\"btrfs: always detect conflicting inodes when logging inode refs\")\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": "63a29724a85f1999e49bf0a9bf0d22643b6116e5", "tree": "d08ca18d6efb587209dd43f5498e6840c73ab4a7", "parents": [ "e45c90fedb0b6107ea73ee2812ce823f4f2a0f6e" ], "author": { "name": "Viacheslav Dubeyko", "email": "slava@dubeyko.com", "time": "Wed Dec 24 00:31:21 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jan 01 13:14:26 2026" }, "message": "xfstests: add HFS/HFS+ and NILFS2 into supported FS table\n\nThis patch adds HFS/HFS+ and NILFS2 file systems\ninto supported FS table with L1 level.\n\nSigned-off-by: Viacheslav Dubeyko \u003cslava@dubeyko.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "e45c90fedb0b6107ea73ee2812ce823f4f2a0f6e", "tree": "6b043015e3863bf9f5f991422af79542cab163e5", "parents": [ "71131073bc76e4559b9689625687e063c4704ba9" ], "author": { "name": "Viacheslav Dubeyko", "email": "slava@dubeyko.com", "time": "Wed Dec 24 00:29:58 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jan 01 13:14:26 2026" }, "message": "generic/020: limit xattr value by 3802 bytes\n\nHFS+ implementation supports only inline extended attributes.\nThe size of value for inline xattr is limited by 3802 bytes [1].\n\n[1] https://elixir.bootlin.com/linux/v6.19-rc2/source/include/linux/hfs_common.h#L626\n\nSigned-off-by: Viacheslav Dubeyko \u003cslava@dubeyko.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "71131073bc76e4559b9689625687e063c4704ba9", "tree": "ef407fee5048ff9cc250b6788e97c24b3da77ac5", "parents": [ "4c7968b86932ad2e8ae6fa480896ec7174dec9df" ], "author": { "name": "Chao Yu", "email": "chao@kernel.org", "time": "Tue Dec 09 07:50:28 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jan 01 13:14:26 2026" }, "message": "common/quota: fix to wait for all inodes been evicted in _check_quota_usage()\n\ngeneric/233 3s ... - output mismatch (see /share/git/fstests/results//generic/233.out.bad)\n --- tests/generic/233.out 2025-01-12 21:57:40.259440359 +0800\n +++ /share/git/fstests/results//generic/233.out.bad 2025-12-04 03:02:26.000000000 +0800\n @@ -4,4 +4,12 @@\n\n seed \u003d S\n Comparing user usage\n +4c4\n +\u003c #1000 -- 31476 32000 32000 994 1000 1000\n +---\n +\u003e #1000 -- 31476 32000 32000 944 1000 1000\n ...\n (Run \u0027diff -u /share/git/fstests/tests/generic/233.out /share/git/fstests/results//generic/233.out.bad\u0027 to see the entire diff)\nRan: generic/233\nFailures: generic/233\nFailed 1 of 1 tests\n\nSometimes, generic/233 will fail due to it founds inode count is mismatched\nin between quota system and filesystem.\n\nThe reason is cgroup v2 implementation will increase inode reference first,\nand then, attach it to thread related cgroup writeback structure, once it\nneeds to switch write owner of target inode, a kernel thread will process\nit, and finally release inode reference via evict_inode().\n\nSo, sync \u0026 drop_cache may not guarantee all inodes being evicted, as cgroup\nhas one more referenece on inodes during the time.\n\nIf inode has not been evicted, dquot inode reference will not be release, it\nwill lead to inode count mismatch.\n\nLet\u0027s add a delay to wait for cgroup switching completion before quota check.\n\nCc: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\nCc: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Chao Yu \u003cchao@kernel.org\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "4c7968b86932ad2e8ae6fa480896ec7174dec9df", "tree": "06564d39359f1a551dfcc74a9b36a429a1a46620", "parents": [ "80259c855ad782c66133e5ed06cf569857dd1f97" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Tue Dec 09 08:25:04 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jan 01 13:14:26 2026" }, "message": "fstests: btrfs/226: skip the test for bs \u003e ps cases\n\n[RANDOM FAILURE]\nSometimes btrfs/226 can fail but sometimes it can also pass with 8K\nfs block size and 4K page size:\n\n[adam@btrfs-vm xfstests]$ sudo ./check btrfs/226\nFSTYP -- btrfs\nPLATFORM -- Linux/x86_64 btrfs-vm 6.18.0-custom+ #323 SMP PREEMPT_DYNAMIC Mon Dec 8 07:38:30 ACDT 2025\nMKFS_OPTIONS -- -s 8k /dev/mapper/test-scratch1\nMOUNT_OPTIONS -- /dev/mapper/test-scratch1 /mnt/scratch\n\nbtrfs/226 2s ... 3s\nRan: btrfs/226\nPassed all 1 tests\n\n[adam@btrfs-vm xfstests]$ sudo ./check btrfs/226\nFSTYP -- btrfs\nPLATFORM -- Linux/x86_64 btrfs-vm 6.18.0-custom+ #323 SMP PREEMPT_DYNAMIC Mon Dec 8 07:38:30 ACDT 2025\nMKFS_OPTIONS -- -s 8k /dev/mapper/test-scratch1\nMOUNT_OPTIONS -- /dev/mapper/test-scratch1 /mnt/scratch\n\nbtrfs/226 3s ... - output mismatch (see /home/adam/xfstests/results//btrfs/226.out.bad)\n --- tests/btrfs/226.out\t2024-04-12 14:04:03.080000035 +0930\n +++ /home/adam/xfstests/results//btrfs/226.out.bad\t2025-12-09 18:46:44.416878799 +1030\n @@ -39,14 +39,11 @@\n Testing write against prealloc extent at eof\n wrote 65536/65536 bytes at offset 0\n XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)\n -wrote 65536/65536 bytes at offset 65536\n -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)\n +pwrite: Resource temporarily unavailable\n File after write:\n ...\n (Run \u0027diff -u /home/adam/xfstests/tests/btrfs/226.out /home/adam/xfstests/results//btrfs/226.out.bad\u0027 to see the entire diff)\nRan: btrfs/226\nFailures: btrfs/226\nFailed 1 of 1 tests\n\n[CAUSE]\nFor the failure case, the failure is from check_direct_IO(), which find\nout that the buffer provided is only aligned to PAGE_SIZE (4K), not to the\nfs block size (8K).\n\nThe user space can only ensure the allocated memory is contiguous in the\nuser space, but the user space can not ensure the underlying physical\nmemory layout, thus depending on the memory allocation situation, the\nuser space can not always get physically contiguous memory, and fail the\ncheck_direct_IO() call.\n\nAfter failed check_direct_IO(), we fall back to buffered IO, but since\nthis particular test case is using RWF_NOWAIT, rejecting buffered IO\nfallback, the direct IO failed with -EAGAIN.\n\n[FIX]\nSince we can not ensure the physical memory layout for direct IO, just\nskip this test case if the fs block size is larger than page size.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: David Sterba \u003cdsterba@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "80259c855ad782c66133e5ed06cf569857dd1f97", "tree": "acb2f99132f09e5f2b336a3f8ad2e10c665115f7", "parents": [ "657410a19ab577a946d1d8ba94e0254b5a034ab1" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Tue Dec 09 08:52:13 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jan 01 13:14:26 2026" }, "message": "fstests: btrfs/301: use correct blocksize to fill the fs\n\n[FAILURE]\nWhen running the test with 8K fs block size (tried both 4K page size and\n64K page size), the test case btrfs/301 always fail like this:\n\nFSTYP -- btrfs\nPLATFORM -- Linux/x86_64 btrfs-vm 6.18.0-custom+ #323 SMP PREEMPT_DYNAMIC Mon Dec 8 07:38:30 ACDT 2025\nMKFS_OPTIONS -- -s 8k /dev/mapper/test-scratch1\nMOUNT_OPTIONS -- /dev/mapper/test-scratch1 /mnt/scratch\n\nbtrfs/301 42s ... - output mismatch (see /home/adam/xfstests/results//btrfs/301.out.bad)\n --- tests/btrfs/301.out\t2024-01-02 14:44:11.140000000 +1030\n +++ /home/adam/xfstests/results//btrfs/301.out.bad\t2025-12-09 19:14:32.057824678 +1030\n @@ -1,18 +1,71 @@\n QA output created by 301\n basic accounting\n +subvol 256 mismatched usage 41099264 vs 33964032 (expected data 33554432 expected meta 409600 diff 7135232)\n +subvol 256 mismatched usage 175316992 vs 168181760 (expected data 167772160 expected meta 409600 diff 7135232)\n +subvol 256 mismatched usage 41099264 vs 33964032 (expected data 33554432 expected meta 409600 diff 7135232)\n +subvol 256 mismatched usage 41099264 vs 33964032 (expected data 33554432 expected meta 409600 diff 7135232)\n fallocate: Disk quota exceeded\n ...\n (Run \u0027diff -u /home/adam/xfstests/tests/btrfs/301.out /home/adam/xfstests/results//btrfs/301.out.bad\u0027 to see the entire diff)\n\n[CAUSE]\nAlthough the subvolume usage doesn\u0027t match the expectation, \"btrfs check\"\ndoesn\u0027t report any qgroup number mismatch.\nThis means the qgroup numbers are correct, but our expectation is not.\n\nUpon inspection of the on-disk file extents, there are a lot of file\nextents that are partially overwritten.\n\nThis means during the fio random writes, there are fs blocks that are\npartially written, then written back to the storage, then written again.\nThis is a symptom of too small IO block size.\n\nThe default FIO blocksize is only 4K, and it will result the above\noverwrite of the same fs block for 8K fs block size.\n\n[FIX]\nAdd blocksize option to the fio config, so that we won\u0027t have\nabove over-write behavior which boost the qgroup numbers.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: David Sterba \u003cdsterba@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "657410a19ab577a946d1d8ba94e0254b5a034ab1", "tree": "945a40ecb64833469fba3a3454e10fca562622ae", "parents": [ "1da7f10cd89d3392f68cadf7c08f43107c9c0295" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Fri Dec 05 07:17:26 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Jan 01 13:14:26 2026" }, "message": "fstests: generic/746: update the parser to handle block group tree\n\n[FALSE ALERT]\nThe test case will fail on btrfs if the new block-group-tree feature is\nenabled:\n\nFSTYP -- btrfs\nPLATFORM -- Linux/x86_64 btrfs-vm 6.18.0-rc6-custom+ #321 SMP PREEMPT_DYNAMIC Sun Nov 23 16:34:33 ACDT 2025\nMKFS_OPTIONS -- -O block-group-tree /dev/mapper/test-scratch1\nMOUNT_OPTIONS -- /dev/mapper/test-scratch1 /mnt/scratch\n\ngeneric/746 44s ... [failed, exit status 1]- output mismatch (see xfstests-dev/results//generic/746.out.bad)\n --- tests/generic/746.out\t2024-06-27 13:55:51.286338519 +0930\n +++ xfstests-dev/results//generic/746.out.bad\t2025-11-28 07:47:17.039827837 +1030\n @@ -2,4 +2,4 @@\n Generating garbage on loop...done.\n Running fstrim...done.\n Detecting interesting holes in image...done.\n -Comparing holes to the reported space from FS...done.\n +Comparing holes to the reported space from FS...Sectors 256-2111 are not marked as free!\n ...\n (Run \u0027diff -u xfstests-dev/tests/generic/746.out xfstests-dev/results//generic/746.out.bad\u0027 to see the entire diff)\n\n[CAUSE]\nSectors [256, 2048) are the from the reserved first 1M free space.\nSectors [2048, 2112) are the leading free space in the chunk tree.\nSectors [2112, 2144) is the first tree block in the chunk tree.\n\nHowever the reported free sectors from get_free_sectors() looks like this:\n\n 2144 10566\n 10688 11711\n ...\n\nNote that there should be a free sector range in [2048, 2112) but it\u0027s\nnot reported in get_free_sectors().\n\nThe get_free_sectors() call is fs dependent, and for btrfs it\u0027s using\nparse-extent-tree.awk script to handle the extent tree dump.\n\nThe script uses BLOCK_GROUP_ITEM items to detect the beginning of a\nblock group so that it can calculate the hole between the beginning of a\nblock group and the first data/metadata item.\n\nHowever block-group-tree feature moves BLOCK_GROUP_ITEM items to a\ndedicated tree, making the existing script unable to parse the free\nspace at the beginning of a block group.\n\n[FIX]\nIntroduce a new script, parse-free-space.py, that accepts two tree\ndumps:\n\n- block group tree dump\n If the fs has block-group-tree feature, it\u0027s the block group tree\n dump.\n Otherwise the regular extent tree dump is enough.\n\n- extent tree dump\n The usual extent tree dump.\n\nWith a dedicated block group tree dump, the script can correctly handle\nthe beginning part of free space, no matter if block-group-tree feature\nis enabled or not.\n\nAnd with this parser, the old parse-extent-tree.awk can be retired.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: David Sterba \u003cdsterba@suse.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "1da7f10cd89d3392f68cadf7c08f43107c9c0295", "tree": "6e027dae80ecd1380b3e31ef3b0ec4fbecd4a852", "parents": [ "ad2b96dd66ef34798c83aef841930bf90797b874" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Thu Dec 04 04:41:08 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 22:33:54 2025" }, "message": "fstests: btrfs: add a new test case to verify quick qgroup inherit\n\n[BUG]\nThere is a bug report that simple quota exposed a bug in the quick\nqgroup inherit, that if there is a multi-level qgroup parent\nrelationship, only the direct parent got updated.\n\n[TEST CASE]\nThe test case will create the following subvolume and qgroups first:\n\n- A new subvolume at \u0027/subv1\u0027\n- Qgroup 1/1\n- Qgroup 2/1\n\nAnd subvolume \u0027/subv1\u0027 is assgiend to qgroup 1/1, so 1/1 is the direct\nparent.\nThen qgroup 1/1 is also assigned to 2/1, so 2/1 is an indirect parent of\nsubvolume \u0027/subv1\u0027.\n\nThen the trigger part is to creating a snapshot of \u0027/subv1\u0027 and also\nassigned the new snapshot into qgroup 1/1 during the snapshot creation.\n\nSince 1/1 is the parent of \u0027/subv1\u0027 and the new snapshot, and qgroup 1/1\nfully owns \u0027/subv1\u0027, we can do a quick inherit.\n\nAfter the triggering part, just finish the test case and the fsck after\nthe test case should detect any qgroup inconsistency.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: David Sterba \u003cdsterba@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "ad2b96dd66ef34798c83aef841930bf90797b874", "tree": "fd973adc3e99ebaa9c7e316d13692a54e508e363", "parents": [ "fb14379b8dbcc96b58773934ed1e2e31288e6d96" ], "author": { "name": "Anthony Iliopoulos", "email": "ailiop@suse.com", "time": "Wed Dec 17 11:08:19 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 22:27:14 2025" }, "message": "xfs/490: fix failure due to deprecated ikeep mount option\n\nThe ikeep mount option has been deprecated as of kernel commit\nb9a176e54162 (\"xfs: remove deprecated mount options\"), and after commit\n3e7ec343f066 (\"xfs: loudly complain about defunct mount options\") there\nis a warning emitted when testing v5 filesystems.\n\nFix it by explicitly requiring and formatting scratch to nocrc/v4, as\nthe test cannot otherwise be triggered on v5 without the ikeep option.\n\nSigned-off-by: Anthony Iliopoulos \u003cailiop@suse.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "fb14379b8dbcc96b58773934ed1e2e31288e6d96", "tree": "a920dad1ad83079d8d8cb22c17a7b5b7ff2def55", "parents": [ "fdc576ef62e27179e4b606e6b4797a1b38ea2f7a" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Wed Dec 10 05:51:34 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 22:26:41 2025" }, "message": "MAINTAINERS: update entry for Anand Jain\n\nThe oracle address bounces. Replaced it with the kernel.org address\nfound in recent commit logs.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "fdc576ef62e27179e4b606e6b4797a1b38ea2f7a", "tree": "c6e567311c1d00e19703c73eeef8b825cd69040f", "parents": [ "d49e334213756882160117c27afa5c3b627760e6" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Dec 16 18:29:56 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 22:19:31 2025" }, "message": "xfs/649: fix various problems\n\nFix a couple of problems with this new test:\n\nFirst, the comment for the $attr_size_bytes check says that the maximum\nsize of a single xattr value is 64k. This is true, but the check\ntriggers the warning even when the size is exactly 64k.\n\nSecond, the test fails to format with 32k and 64k fsblock size\nfilesystems because the scsi_debug device size is 128M, and that\u0027s not\nlarge enough for the minimum log size. Raise that to 320M.\n\nCc: fstests@vger.kernel.org # v2025.12.09\nFixes: 5760b2105985bf (\"xfs: test case for handling io errors when reading extended attributes\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "d49e334213756882160117c27afa5c3b627760e6", "tree": "bf5cec9ec819aeb029e1e60607708b157bcc836a", "parents": [ "36836607c9e79c9d18de5affcc05ce723ad16a7b" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Dec 16 18:29:41 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 22:19:31 2025" }, "message": "common/rc: fix _xfs_is_realtime_file for internal rt devices\n\nNow that we can have internal realtime devices, it\u0027s possible to have a\nrealtime filesystem without setting USE_EXTERNAL\u003dyes or SCRATCH_RTDEV.\nUse the existing _xfs_has_feature helper to figure out if the given path\npoints to a filesystem with an online realtime volume.\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": "36836607c9e79c9d18de5affcc05ce723ad16a7b", "tree": "eb8173f757a04295e30f4c2ac3e6cfe0738e648c", "parents": [ "1a1521a039d43a106b301bef17267c82686ddf6a" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Dec 16 18:29:25 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 22:19:31 2025" }, "message": "check: put temporary files in TMPDIR, not /tmp\n\nNowadays, systemd will auto-remove files from /tmp after 10 days. If\nyou want to run a testcase for more than that duration (e.g.\nSOAK_DURATION\u003d14d) then the test will fail after the .out file is\ndeleted:\n\n xfs/286 _check_xfs_filesystem: filesystem on /dev/sda4 is inconsistent (r)\n (see /var/tmp/fstests/xfs/286.full for details)\n sed: can\u0027t read /tmp/2098.out: No such file or directory\n - output mismatch (see /var/tmp/fstests/xfs/286.out.bad)\n mv: cannot stat \u0027/tmp/2098.out\u0027: No such file or directory\n diff: /var/tmp/fstests/xfs/286.out.bad: No such file or directory\n\nThis happens because systemd-tmpfiles garbage collects any file in /tmp\nthat becomes older than 10 days:\n\n $ cat /usr/lib/tmpfiles.d/tmp.conf\n # This file is part of systemd.\n #\n # systemd is free software; you can redistribute it and/or modify it\n # under the terms of the GNU Lesser General Public License as published by\n # the Free Software Foundation; either version 2.1 of the License, or\n # (at your option) any later version.\n\n # See tmpfiles.d(5) for details.\n\n # Clear tmp directories separately, to make them easier to override\n q /tmp 1777 root root 10d\n q /var/tmp 1777 root root 30d\n\nThis is now the default in Debian 13 (D12 never deleted anything) which\nis why I didn\u0027t notice this until I upgraded a couple of weeks ago.\nMost people aren\u0027t going to be running a single testcase for more than\n10 days so I\u0027ll go with the least invasive solution that I can think of.\n\nAllow system administrators or fstests runners to set TMPDIR to a\ndirectory that won\u0027t get purged, and make fstests follow that. Fix up\ngeneric/002 so that it doesn\u0027t use $tmp for paths on the test\nfilesystem.\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": "1a1521a039d43a106b301bef17267c82686ddf6a", "tree": "63bd3f7c39e571d626e1eafef708fd1eed281ffd", "parents": [ "cfb2146bc959fde3633bcec1ed53f359babea4cb" ], "author": { "name": "Anand Jain", "email": "asj@kernel.org", "time": "Wed Dec 17 17:00:22 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 22:18:07 2025" }, "message": "fstests: fix flaky device name in _cleanup_flakey\n\nThere is no device named flakey-test, which _cleanup_flakey() currently\nuses. The actual device name is stored in $FLAKEY_NAME and is set to\nflakey-test.$seq. Use $FLAKEY_NAME instead.\n\nSigned-off-by: Anand Jain \u003casj@kernel.org\u003e\nFixes: 603030dee015ba (\"fstests: per-test dmflakey instances\")\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": "cfb2146bc959fde3633bcec1ed53f359babea4cb", "tree": "4f58bf2aa81dfa862a120c6e82c286da0068e97a", "parents": [ "90f6065005e7feec44a0fa45785284df3a1b525d" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:11 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "xfs/650: require a real SCRATCH_RTDEV\n\nRequire a real SCRATCH_RTDEV instead of faking one up using a loop\ndevice, as otherwise the options specified in MKFS_OPTIONS might\nnot actually work the configuration.\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": "90f6065005e7feec44a0fa45785284df3a1b525d", "tree": "f3b1d679af471570f237f796308be6e2ba3a1348", "parents": [ "70824203cb6827179236de0b37ea41123cbe462e" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:10 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "xfs/530: require a real SCRATCH_RTDEV\n\nRequire a real SCRATCH_RTDEV instead of faking one up using a loop\ndevice, as otherwise the options specified in MKFS_OPTIONS might\nnot actually work the configuration.\n\nNote that specifying a rtextsize doesn\u0027t work for zoned file systems,\nso _notrun when mkfs fails.\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": "70824203cb6827179236de0b37ea41123cbe462e", "tree": "7efdb3246b0f79347a185bfa60771b2472dc939c", "parents": [ "e157f480a308e0c9e4d8abcc8c3f6463c61905fc" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:09 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "xfs/528: require a real SCRATCH_RTDEV\n\nRequire a real SCRATCH_RTDEV instead of faking one up using a loop\ndevice, as otherwise the options specified in MKFS_OPTIONS might\nnot actually work the configuration.\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": "e157f480a308e0c9e4d8abcc8c3f6463c61905fc", "tree": "cd7a9f4b4a6d68d43212b5515c4bcfd0c045f2ff", "parents": [ "0d89f8063ece5ece81d44acef2dbd51bc74f8ae5" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:08 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "xfs/521: call _require_scratch_size\n\nThis tests expects to have at least 400M on the scratch device.\nEnsure that, even if test runs with small devices will probably\nbreak in all kinds of other funny ways.\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": "0d89f8063ece5ece81d44acef2dbd51bc74f8ae5", "tree": "705b43ff3bc597d3b66889a90f5d7125747e951d", "parents": [ "30ee67e320de8af77f28c96d280f34c606b54d6a" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:07 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "xfs/521: require a real SCRATCH_RTDEV\n\nRequire a real SCRATCH_RTDEV instead of faking one up using a loop\ndevice, as otherwise the options specified in MKFS_OPTIONS might\nnot actually work the configuration.\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": "30ee67e320de8af77f28c96d280f34c606b54d6a", "tree": "5bb2329a1ff1ce3430a64be04d301a51e4cf5e1b", "parents": [ "4460f5d01c7e6f1ac62fd9d62f7f9c300d998e6e" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:06 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "xfs/424: don\u0027t use SCRATCH_DEV helpers\n\nThis tests forces external devices to be disabled by calling mkfs.xfs\ndirectly and overriding SCRATCH_{LOG,RT}DEV, but the options specified in\nMKFS_OPTIONS might not work for this configuration. Instead hard code\nthe calls to xfs_db and don\u0027t modify the scratch device configuration.\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": "4460f5d01c7e6f1ac62fd9d62f7f9c300d998e6e", "tree": "0432032e4a55e2062b5bf38155a30d5c85d905f3", "parents": [ "255cb1f0dd6e9c604f01acc49b1d735916e80514" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:05 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "xfs/185: don\u0027t use SCRATCH_{,RT}DEV helpers\n\nThis tests creates loop-based data and rt devices for testing. Don\u0027t\noverride SCRATCH_{,RT}DEV and don\u0027t use the helpers based on it because\nthe options specified in MKFS_OPTIONS might not work for this\nconfiguration. This also means that we will now never use a log device\nfor this test even if SCRATCH_LOGDEV was set, which is fine because the\nlog device is not relevant for what is tested.\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": "255cb1f0dd6e9c604f01acc49b1d735916e80514", "tree": "a66c8336bee23072c926eb110aad2a3ccdda2ecb", "parents": [ "901f00980f0e0cc28d15e9a4865d1a58d8c35af5" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:04 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "xfs/157: don\u0027t override SCRATCH_{,LOG,RT}DEV\n\nThis tests wants to test various difference device configurations,\nand does so by overriding SCRATCH_{,LOG,RT}DEV. This has two downside:\n\n 1) the actual SCRATCH_{,LOG,RT}DEV configuration is still injected by\n default, thus making the test dependent on that configuration\n 2) the MKFS_OPTIONS might not actually be compatible with the\n configuration created\n\nFix this by open coding the mkfs, db, admin and repair calls and always\nrun them on the specific configuration.\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": "901f00980f0e0cc28d15e9a4865d1a58d8c35af5", "tree": "b952150f8e5e87e46e1b74056f1f59b942c18adf", "parents": [ "cd74736e17949b32c6e680b8f83755f147558a6f" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:03 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "generic/590: split XFS RT specific bits out\n\nCurrently generic/590 runs a very different test on XFS that creates\na lot device and so on. Split that out into a new XFS-specific test,\nand let generic/590 always run using the file system parameter specified\nin the config even for XFS.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "cd74736e17949b32c6e680b8f83755f147558a6f", "tree": "649ea02acaa4ad2d92e6193b7e245a41d918ffdc", "parents": [ "a63b4556fc740792188a56b2ae61afb6b02635ac" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:02 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "ext4/032: use _check_dev_fs\n\n_check_dev_fs is the new designated helper to check file systems on\narbitrary devices, use that instead of _check_generic_filesystem, which\nis just an implementation detail.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "a63b4556fc740792188a56b2ae61afb6b02635ac", "tree": "e09b31760894402b59b11aa2d45ca31ce84e2419", "parents": [ "5dbc7499a3b2e4a99c02c1b45c3a2d33d443a8b6" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:01 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "common: add a _check_dev_fs helper\n\nAdd a helper to run the file system checker for a given device, and stop\noverloading _check_scratch_fs with the optional device argument that\ncreates complication around scratch RT and log devices.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "5dbc7499a3b2e4a99c02c1b45c3a2d33d443a8b6", "tree": "88256054b1fe94496c8b27016d67765c68e27617", "parents": [ "eb2ad950ea90d8d8d861f8beac138d6a19f0f819" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:30:00 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "ext4/006: call e2fsck directly\n\n_check_scratch_fs takes an optional device name, but no optional\narguments. Call e2fsck directly for this extN-specific test instead.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "eb2ad950ea90d8d8d861f8beac138d6a19f0f819", "tree": "4a737e99819ad27108238529fa09df05388cda5d", "parents": [ "7e972aff4801afb44b9faea4a7598a311b887fc0" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Thu Dec 18 07:29:59 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 21:02:23 2025" }, "message": "dmflakey: override SCRATCH_DEV in _init_flakey\n\n_init_flakey already overrides SCRATCH_LOGDEV and SCRATCH_RTDEV so that\nthe XFS-specific helpers work fine with external devices. Do the same\nfor SCRATCH_DEV itself, so that _scratch_mount and _scratch_unmount just\nwork, and so that _check_scratch_fs does not need to override the main\ndevice.\n\nThis requires some small adjustments in how generic/741 checks that\nmounting the underlying device fails, but the new version actually is\nsimpler than the old one, and in xfs/438 where we need to be careful\nwhere to create the custom dm table.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nReviewed-by: Anand Jain \u003casj@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "7e972aff4801afb44b9faea4a7598a311b887fc0", "tree": "7b4babeadc6f9fa6fbc1131d31edf14be64aafe7", "parents": [ "960384aa2c46622dc0048f417a18be2d09166f83" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Fri Dec 19 05:35:46 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 20:59:50 2025" }, "message": "xfs: test that mkfs creates zone-aligned RT devices\n\nMake sure mkfs doesn\u0027t create unmountable file systems and instead rounds\ndown the RT subvolume size to a multiple of the zone size.\n\nTwo passes: one with a device that is not aligned, and one for an\nexplicitly specified unaligned RT device size.\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": "960384aa2c46622dc0048f417a18be2d09166f83", "tree": "89b7faf43fb8eca2c6c962927979dd95596cb1f1", "parents": [ "f4ec120ffd251564cc78d6d0dae78ca93cb5b648" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Fri Dec 19 05:35:45 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 20:59:50 2025" }, "message": "xfs: test that RT growfs not aligned to zone size fails\n\nCheck that a file system with a zoned RT subvolume can\u0027t be resized to\na size not aligned to the zone size.\n\nUses a zloop device so that we can control the exact zone size.\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": "f4ec120ffd251564cc78d6d0dae78ca93cb5b648", "tree": "de74f1991e9c60e665bf1903fed2adc79a7eb053", "parents": [ "f02d4965d48f59f53a729e9ddd55fb8fcc373f85" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Fri Dec 19 05:35:44 2025" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Dec 31 20:59:50 2025" }, "message": "xfs: add a test that zoned file systems with rump RTG can\u0027t be mounted\n\nGarbage collection assumes all zones contain the full amount of blocks.\nMkfs already ensures this happens, but the kernel mount code did not\nverify this. Instead such a file system would eventually fail scrub.\n\nAdd a test to verify the new superblock verifier check.\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" } ], "next": "f02d4965d48f59f53a729e9ddd55fb8fcc373f85" }