)]}' { "log": [ { "commit": "bb04d577435d04ce3aa160f0563d1d35d4860d54", "tree": "7fa8b4575e7193b68173d61fc3edf3dbaf63e81e", "parents": [ "298f60c81a93fabde5f87f6a99fea158f9c4ff24" ], "author": { "name": "Josef Bacik", "email": "josef@toxicpanda.com", "time": "Thu Apr 28 11:05:00 2022 -0400" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Fri Apr 29 16:09:12 2022 +0800" }, "message": "fstests: add some missing _require_loop\u0027s\n\nGot a new box running overnight fstests and noticed a couple of failures\nbecause I forgot to enable loop device support. Fix these two tests to\nhave _require_loop so they don\u0027t fail if there\u0027s no loop device support.\n\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "298f60c81a93fabde5f87f6a99fea158f9c4ff24", "tree": "0ae27350c4755efaf242a14fccce6fb94d56a63e", "parents": [ "ab47e281b70faa797485714802474af8d3d4a2b1" ], "author": { "name": "Yang Xu", "email": "xuyang2018.jy@fujitsu.com", "time": "Tue Apr 26 16:55:45 2022 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Apr 28 23:02:34 2022 +0800" }, "message": "generic/673: Add separate sgid stripping sub-tests\n\nEven kernel doesn\u0027t get ATTR_KILL_SGID mask and get ATTR_KILL_SUID mask,\nwe still can strip S_ISGID mode in setattr_prepare and setattr_copy.\n\nWe should check separate sgid stripping logic whether works well\non different filesystems.\n\nAlso fix comments error.\n\nSigned-off-by: Yang Xu \u003cxuyang2018.jy@fujitsu.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "ab47e281b70faa797485714802474af8d3d4a2b1", "tree": "7f41e14dc9ec4196527125b2c100c37a84875d21", "parents": [ "987700db300da0d2a93fba25cfdcf912633e5621" ], "author": { "name": "Zorro Lang", "email": "zlang@redhat.com", "time": "Tue Apr 26 14:24:11 2022 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Thu Apr 28 22:51:31 2022 +0800" }, "message": "fsstress: remove ALLOCSP and FREESP operations entirely\n\nDue to upstream linux has removed ALLOCSP/FREESP ioctls by commit:\n4d1b97f9ce7c0 (\"xfs: kill the XFS_IOC_{ALLOC,FREE}SP* ioctls\"), so\nlet\u0027s remove ALLOCSP/FREESP testing from fsstress, to avoid more\nmismatch problems.\n\nDue to g/070 specified \"-f allocsp\" and \"-f freesp\u003d0\", so remove\nthese two lines too.\n\nSigned-off-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": "987700db300da0d2a93fba25cfdcf912633e5621", "tree": "7be80a7be0eae78504a3ec7c0c2a439f0d314f9f", "parents": [ "7753e08d22e97d50a851f79c6304bcbf9b2949cc" ], "author": { "name": "Chung-Chiang Cheng", "email": "cccheng@synology.com", "time": "Mon Apr 25 12:22:26 2022 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:01 2022 +0800" }, "message": "fstests: btrfs: test setting compression via xattr on nodatacow files\n\nCompression and nodatacow are mutually exclusive. Besides ioctl, there\nis another way to setting compression via xattrs, and shouldn\u0027t produce\ninvalid combinations.\n\nSigned-off-by: Chung-Chiang Cheng \u003ccccheng@synology.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "7753e08d22e97d50a851f79c6304bcbf9b2949cc", "tree": "5f1c2b942c05510148665a38ff3d009b3decc152", "parents": [ "5528f7843b1ad6f15a9d6ac050cfdd6ce5b229f9" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Tue Apr 26 00:14:53 2022 -0500" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:01 2022 +0800" }, "message": "fstests: remove xfs/144\n\nThis test was designed to validate the quota warning limit, which in\ntheory was supposed to migrate from a soft quota to hard enforcement\nafter a certain number of warnings. However, the xfs kernel commit\nwhich incremented the warning counter was reverted; see:\n\nxfs: revert \"xfs: actually bump warning counts when we send warnings\"\n\nin the kernel tree for an explanation of why. Due to that revert,\nwhich removed this functionality, remove this test.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\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": "5528f7843b1ad6f15a9d6ac050cfdd6ce5b229f9", "tree": "8093e593a9db3ddaed6fa59b8578bb21ccdd3de8", "parents": [ "0fd8e26141f50aaba8c6d3e058149a499317e445" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Apr 25 17:14:50 2022 -0400" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:00 2022 +0800" }, "message": "generic/681, generic/682: add debugging information to $seqreq.full\n\nThese two tests are checking whether a non-privileged user causing a\nblock allocation while expanding a directory block when over quota\nwill fail with an EDQUOT error. There are three reasons why this can\nfail.\n\n* Aa test bug, where if the file system is using cluster allocation\n (for example, ext4 bigalloc) the test doesn\u0027t add enough directory\n entries to actually force directory grwoth.\n\n* A file system bug, where the file system allocates blocks but for\n some reason isn\u0027t charging the space quota correctly (which\n currently seems to be the case in ext4 with fscrypt).\n\n* A file system bug, where the file system is correctly charging the\n space quota to the unprivileged user, but isn\u0027t failing the system\n call with EDQUOT.\n\nBy adding some additional debugging information about whether\ndirectory has grown or not (in addition to the existing repquota\noutput) to the the $seqres.full, it makes easier for the file system\ndeveloper to disambiguate between these possibilities. It\u0027s cheap to\ndo this, and it could save developer time when trying to root cause\nthe failure.\n\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nCc: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "0fd8e26141f50aaba8c6d3e058149a499317e445", "tree": "5fdbe40e800215bee5bf6e3b183e6ae3447837b3", "parents": [ "31c01ce18f733117bda68870d42d78a88b93c97d" ], "author": { "name": "Murphy Zhou", "email": "jencce.kernel@gmail.com", "time": "Mon Apr 25 16:20:51 2022 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:00 2022 +0800" }, "message": "chown: fix ownership format string\n\nAfter coreutils rebasing to 9.1, chown(1) behavior changes:\n\"\n chown and chroot now warn about usages like \"chown root.root f\",\n which have the nonstandard and long-obsolete \".\" separator that\n causes problems on platforms where user names contain \".\".\n Applications should use \":\" instead of \".\".\n\"\n\nhttps://lwn.net/Articles/891574/\n\nWith this behavior change, old format of ownership string will cause\nwarning like this:\n\"\n+chown: warning: \u0027.\u0027 should be \u0027:\u0027: \u00271000.1000\u0027\n+.chown: warning: \u0027.\u0027 should be \u0027:\u0027: \u00271100.1100\u0027\n+.chown: warning: \u0027.\u0027 should be \u0027:\u0027: \u00271200.1200\u0027\n+.chown: warning: \u0027.\u0027 should be \u0027:\u0027: \u00271300.1300\u0027\n+.chown: warning: \u0027.\u0027 should be \u0027:\u0027: \u00271400.1400\u0027\n\"\n\nThe new format works fine with old versions of coreutils.\n\nSigned-off-by: Murphy Zhou \u003cjencce.kernel@gmail.com\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "31c01ce18f733117bda68870d42d78a88b93c97d", "tree": "9c9e6b4263362297d141593615a9a450ac267876", "parents": [ "e81417a0964a36aed4392326f3736c116296f451" ], "author": { "name": "Christian Brauner", "email": "brauner@kernel.org", "time": "Wed Apr 20 19:52:22 2022 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:00 2022 +0800" }, "message": "generic: add test for tmpfs POSIX ACLs\n\nAdd a regression test for commit 705191b03d50 (\"fs: fix acl translation\").\nThis tests whether setting POSIX ACLs on a tmpfs mounted in a\nnon-initial user and mount namespace works as expected.\n\nNote, once again the idmapped mount testsuite is grossly misnamed at\nthis point. It has morphed into a full-blown generic vfs feature\ntestsuite.\n\nCc: Eryu Guan \u003cguaneryu@gmail.com\u003e\nCc: Seth Forshee \u003csforshee@digitalocean.com\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\nCc: Zorro Lang \u003czlang@redhat.com\u003e\nCc: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\nSigned-off-by: Christian Brauner (Microsoft) \u003cbrauner@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "e81417a0964a36aed4392326f3736c116296f451", "tree": "3c7e9943e449a7b428727e10246faec5894acd1c", "parents": [ "7f27a290aca8e45ec1f39b631cb6acf923917ca4" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Apr 19 10:32:21 2022 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:00 2022 +0800" }, "message": "generic: ensure we drop suid after fallocate\n\nfallocate changes file contents, so make sure that we drop privileges\nand file capabilities after each fallocate operation.\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": "7f27a290aca8e45ec1f39b631cb6acf923917ca4", "tree": "98df5db53d865ba3ec122419065577cee632fae4", "parents": [ "1dac95cb0d6e97dfa336deab6d13c81aed531666" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Apr 19 10:32:15 2022 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:00 2022 +0800" }, "message": "xfs: make sure syncfs(2) passes back super_operations.sync_fs errors\n\nThis is a regression test to make sure that nonzero error returns from\na filesystem\u0027s -\u003esync_fs implementation are actually passed back to\nuserspace when the call stack involves syncfs(2).\n\n[zlang@ add \u0027_supported_fs xfs\u0027 in case]\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": "1dac95cb0d6e97dfa336deab6d13c81aed531666", "tree": "f554f1909185ac1a58eafc74c034a4df672d5c0a", "parents": [ "ad5f89ef3013d0ce8459cce364d60ec957ea2556" ], "author": { "name": "Rishabh Dave", "email": "ridave@redhat.com", "time": "Tue Apr 19 23:28:11 2022 +0530" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:00 2022 +0800" }, "message": "cephfs: add ceph-fuse suport for ceph-fuse\n\nCurrently tests in xfstests-dev can be executed against CephFS only by\nmounting CephFS using kernel driver. Attempting to run tests against\nCephFS using FUSE doesn\u0027t work because xfstests-dev would remount CephFS\nusing kernel. This patch adds the ability for xfstest-dev code to mount\nCephFS using FUSE.\n\n[Zorro add missed \";;\" in common/rc]\n\nFixes: https://tracker.ceph.com/issues/55354\nSigned-off-by: Rishabh Dave \u003cridave@redhat.com\u003e\nReviewed-by: Jeff Layton \u003cjlayton@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "ad5f89ef3013d0ce8459cce364d60ec957ea2556", "tree": "fcfeaaa9152f68165f87d5b55a02c3111aafa98f", "parents": [ "af8aeeea48d0d876f8f9ecda307b45b655aea6a7" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Apr 19 10:32:06 2022 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:00 2022 +0800" }, "message": "generic/019: fix incorrect unset statements\n\nFix incorrect usage of unset -- one passes the name of the variable, not\nthe *value* contained within it.\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": "af8aeeea48d0d876f8f9ecda307b45b655aea6a7", "tree": "8abf41be23219fa08a25bd92fc4e546d963daad6", "parents": [ "80a82f6926faadc3d44cf07ff22f01943c3471fd" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Apr 19 10:32:00 2022 -0700" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:54:00 2022 +0800" }, "message": "xfs/019: fix golden output for files created in setgid dir\n\nA recent change to xfs/019 exposed a long-standing bug in mkfs where\nit would always set the gid of a new child created in a setgid directory\nto match the gid parent directory instead of what\u0027s in the protofile.\n\nIgnoring the user\u0027s directions is not the correct behavior, so update\nthis test to reflect that. Also don\u0027t erase the $seqres.full file,\nbecause that makes forensic analysis pointlessly difficult.\n\nCc: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nFixes: 7834a740 (\"xfs/019: extend protofile test\")\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "80a82f6926faadc3d44cf07ff22f01943c3471fd", "tree": "2601bd6ab308b3b61d682888fb7947674e98b9a7", "parents": [ "380ee98d92e6b2a8c00458e98531da68b4495c05" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Tue Apr 19 01:03:26 2022 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:43:51 2022 +0800" }, "message": "xfs: test xfsdump when an inode \u003c root inode is present\n\nThis tests a longstanding bug where xfsdumps are not properly\ncreated when an inode is present on the filesytsem which has\na lower number than the root inode.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\n" }, { "commit": "380ee98d92e6b2a8c00458e98531da68b4495c05", "tree": "276152d2a4b7d3f3e921cefdab7aa7395d7103b6", "parents": [ "95c10ab90c2865d0283421e542feec14d46fc597" ], "author": { "name": "Zorro Lang", "email": "zlang@redhat.com", "time": "Thu Apr 21 00:07:56 2022 +0800" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:43:25 2022 +0800" }, "message": "fstests: remove _wipe_fs from dump testing entirely\n\nThe _wipe_fs function in common/dump is a historical remnant of\nxfstests, it\u0027s easy to cause confusion now. Now xfstests tend to\ncall `require_scratch \u0026\u0026 scratch_mkfs \u0026\u0026 scratch_mount` in each case\nitself, we don\u0027t need to use a function to do that specially, so\nremove _wipe_fs entirely.\n\nSigned-off-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\n" }, { "commit": "95c10ab90c2865d0283421e542feec14d46fc597", "tree": "53633704a7c13c4d53cfc94131bc0646650cdece", "parents": [ "858a19c5e9b08a6b8dde818e4452e329664af1fb" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Thu Mar 31 13:19:20 2022 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:42:54 2022 +0800" }, "message": "generic/633: Avoid failure without CONFIG_USER_NS\n\nSome tests in idmapped_mounts fail without CONFIG_USER_NS because they\nhave implicit dependence on user namespaces and these tests are run\ndespite idmapped mount support not being detected. Detect whether at\nleast user namespaces are supported and skip tests needing them when\nthey are not.\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nTested-by: Christian Brauner (Microsoft) \u003cbrauner@kernel.org\u003e\nReviewed-by: Christian Brauner (Microsoft) \u003cbrauner@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "858a19c5e9b08a6b8dde818e4452e329664af1fb", "tree": "9c38b1e8b6fad8ae8264ab781390cbfbe104821d", "parents": [ "fbc6486be09c93a68d3863ebf7e3ed851fc4721c" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Thu Mar 31 13:19:19 2022 +0200" }, "committer": { "name": "Zorro Lang", "email": "zlang@kernel.org", "time": "Wed Apr 27 02:42:02 2022 +0800" }, "message": "idmapped_mounts: Prepare for support for more features\n\nCurrently idmapped_mounts tests fail for kernels without CONFIG_USER_NS\nbecause some tests are run despite missing support for idmapped mounts\nand they implicitely require user namespace support. Prepare\nidmapped_mounts to support more features a test may require to reliably\nrun.\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nTested-by: Christian Brauner (Microsoft) \u003cbrauner@kernel.org\u003e\nReviewed-by: Christian Brauner (Microsoft) \u003cbrauner@kernel.org\u003e\nSigned-off-by: Zorro Lang \u003czlang@kernel.org\u003e\n" }, { "commit": "fbc6486be09c93a68d3863ebf7e3ed851fc4721c", "tree": "ef55b51e3442715b3e5b1e3699f0f24ed8f856e6", "parents": [ "48029933892b96c183603d94a1f3acc179988d99" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Apr 11 15:54:54 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 23:04:25 2022 +0800" }, "message": "generic: test that renaming into a directory fails with EDQUOT\n\nAdd a regression test to make sure that unprivileged userspace renaming\nwithin a directory fails with EDQUOT when the directory quota limits have\nbeen exceeded.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "48029933892b96c183603d94a1f3acc179988d99", "tree": "781d71706a2cff7c5bc9cac2ed0a5b0fedff65dd", "parents": [ "b560e18c6216149e47c5208df2727b01ba2ce49b" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Apr 11 15:54:48 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 23:03:01 2022 +0800" }, "message": "generic: test that linking into a directory fails with EDQUOT\n\nAdd a regression test to make sure that unprivileged userspace linking\ninto a directory fails with EDQUOT when the directory quota limits have\nbeen exceeded.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "b560e18c6216149e47c5208df2727b01ba2ce49b", "tree": "22e3696f3b60ecb8b02b071be0670809dd176e76", "parents": [ "e75da9ebde722455544e7b4e261389d4b77c8a76" ], "author": { "name": "Dave Chinner", "email": "dchinner@redhat.com", "time": "Mon Apr 11 15:48:33 2022 +1000" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 22:47:41 2022 +0800" }, "message": "generic/019: kill background processes on interrupt\n\nIf you ctrl-c generic/019, it leaves fsstress processes running.\nKill them in the cleanup function so that they don\u0027t have to be\nmanually killed after interrupting the test.\n\nWhile touching the _cleanup() function, make it do everything that\nthe generic _cleanup function it overrides does and fix the\nindenting.\n\n[Eryu: unset fs_pid and fio_pid after wait]\n\nSigned-off-by: Dave Chinner \u003cdchinner@redhat.com\u003e\nReviewed-by: David Disseldorp \u003cddiss@suse.de\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "e75da9ebde722455544e7b4e261389d4b77c8a76", "tree": "56096d20fb77ff47505b4fe05c2f9778dc8e0f15", "parents": [ "82047ce7cd46e3a89eaddb6e43e8c10416409cd9" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Fri Apr 15 08:04:58 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 22:38:45 2022 +0800" }, "message": "xfs/216: handle larger log sizes\n\nmkfs will soon refuse to format a log smaller than 64MB, so update this\ntest to reflect the new log sizing calculations.\n\n[Eryu: add xfs/216.cfg and use _link_out_file_name to choose .out file]\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "82047ce7cd46e3a89eaddb6e43e8c10416409cd9", "tree": "f3b1bcb54eef5760245339334f5bb2322c7318b9", "parents": [ "86e537edb41d9fbda0d6a18a8a30fc5c3f49d886" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Apr 11 15:55:08 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 22:20:02 2022 +0800" }, "message": "xfs: test mkfs.xfs config file stack corruption issues\n\nAdd a new regression test for a stack corruption problem uncovered in\nthe mkfs config file parsing code.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "86e537edb41d9fbda0d6a18a8a30fc5c3f49d886", "tree": "38935a8fceb15194fd359d886fd16ce7b030df6d", "parents": [ "0ab8b3ac61ffe7c3b5ac01b6727cc11cddf03384" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Apr 11 15:55:02 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 22:19:16 2022 +0800" }, "message": "common/rc: let xfs_scrub tell us about its unicode checker\n\nNow that xfs_scrub can report whether or not it was built with the\nUnicode name checker, rewrite _check_xfs_scrub_does_unicode to take\nadvantage of that. This supersedes the old method of trying to observe\ndynamic library linkages and grepping the binary, neither of which\nworked very well.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "0ab8b3ac61ffe7c3b5ac01b6727cc11cddf03384", "tree": "437b696d9042fc72cc5105226e8290a064ce4efb", "parents": [ "ca53ba1e74ebbde853dec09fee93b5e730b9ca1e" ], "author": { "name": "Luís Henriques", "email": "lhenriques@suse.de", "time": "Wed Mar 23 16:09:25 2022 +0000" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 21:16:12 2022 +0800" }, "message": "ceph/001: add extra check for remote object copies\n\nCeph kernel client now has a facility to check stats for certain\noperations. One of these operations is the \u0027copyfrom\u0027, the\noperation that is used to offload to the OSDs the copy of objects\nfrom, for example, the copy_file_range() syscall.\n\nThis patch changes ceph/001 to add an extra check to verify that the\ncopies performed by the test are _really_ remote copies and not\nsimple read+write operations.\n\nSigned-off-by: Luís Henriques \u003clhenriques@suse.de\u003e\nReviewed-by: Jeff Layton \u003cjlayton@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "ca53ba1e74ebbde853dec09fee93b5e730b9ca1e", "tree": "8cff4831f8da234589b1492b7f241baa09411eb7", "parents": [ "16676f2f2c3b19f19b5cb259e95139351e6e9bc2" ], "author": { "name": "Eric Whitney", "email": "enwlinux@gmail.com", "time": "Thu Apr 14 10:22:58 2022 -0400" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:32:05 2022 +0800" }, "message": "common/filter: extend _filter_xfs_io to match -nan\n\nWhen run on ext4 with sufficiently fast x86_64 hardware, generic/130\nsometimes fails because xfs_io can report rate values as -nan:\n0.000000 bytes, 0 ops; 0.0000 sec (-nan bytes/sec and -nan ops/sec)\n\n_filter_xfs_io matches the strings \u0027inf\u0027 or \u0027nan\u0027, but not \u0027-nan\u0027. In\nthat case it fails to convert the actual output to a normalized form\nmatching generic/130\u0027s golden output. Extend the regular expression\nused to match xfs_io\u0027s output to fix this.\n\nSigned-off-by: Eric Whitney \u003cenwlinux@gmail.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "16676f2f2c3b19f19b5cb259e95139351e6e9bc2", "tree": "ea0b3ab563fe3164577ee15d43bb0ca78bf46665", "parents": [ "d26e6be1290c27c4639439570ad0c8bf9ce5a5db" ], "author": { "name": "Eric Biggers", "email": "ebiggers@google.com", "time": "Thu Apr 14 00:19:32 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:31:38 2022 +0800" }, "message": "common/encrypt: use a sub-keyring within the session keyring\n\nMake the encryption tests create and use a named keyring \"xfstests\" in\nthe session keyring that the tests happen to be running under, rather\nthan replace the session keyring using \u0027keyctl new_session\u0027.\nUnfortunately, the latter doesn\u0027t work when the session keyring is owned\nby a non-root user, which (depending on the Linux distro) can happen if\nxfstests is run in a sudo \"session\" rather than in a real root session.\n\nThis isn\u0027t a great solution, as the lifetime of the keyring will no\nlonger be tied to the tests as it should be, but it should work. The\nalternative would be the weird hack of making the \u0027check\u0027 script\nre-execute itself using something like \u0027keyctl session - $0 $@\u0027.\n\nReported-by: Ritesh Harjani \u003critesh.list@gmail.com\u003e\nSigned-off-by: Eric Biggers \u003cebiggers@google.com\u003e\n" }, { "commit": "d26e6be1290c27c4639439570ad0c8bf9ce5a5db", "tree": "74b60ee6830102d49a420e6dc944168ea3668427", "parents": [ "d7ac035cfeecc4e3b264bae781aa4eedfd01bf03" ], "author": { "name": "Liu Yiding", "email": "liuyd.fnst@fujitsu.com", "time": "Thu Apr 14 10:34:47 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:30:48 2022 +0800" }, "message": "common/rc: Skip virtiofs when _require_exportfs\n\nopen_by_handle_at(2) is not supported by virtio-fs.\nReference:\nhttps://gitlab.com/virtio-fs/qemu/-/issues/10\n\nSigned-off-by: Liu Yiding \u003cliuyd.fnst@fujitsu.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "d7ac035cfeecc4e3b264bae781aa4eedfd01bf03", "tree": "331a43f84dbcf99989d7d227a274302e315a6d7d", "parents": [ "c025dcf35b47e8d6139554e585e2f7124505c1dd" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Apr 11 15:54:22 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:10:51 2022 +0800" }, "message": "xfs/187: don\u0027t rely on FSCOUNTS for free space data\n\nCurrently, this test relies on the XFS_IOC_FSCOUNTS ioctl to return\naccurate free space information. It doesn\u0027t. Convert it to use statfs,\nwhich uses the accurate versions of the percpu counters. Obviously,\nthis only becomes a problem when we convert the free rtx count to use\n(sloppier) percpu counters instead of the (more precise and previously\nbuggy) ondisk superblock counts.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "c025dcf35b47e8d6139554e585e2f7124505c1dd", "tree": "e40f8eb85cf36efcc0620d0e0b74b32105e04652", "parents": [ "9c6b2ebe2b6b475a53f3f324fb4ddcef4550404b" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Apr 11 15:54:28 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:10:41 2022 +0800" }, "message": "xfs/507: add test to auto group\n\nAdd this regression test to the auto group now that it\u0027s been quite a\nwhile since the fix patches went upstream.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "9c6b2ebe2b6b475a53f3f324fb4ddcef4550404b", "tree": "40e4b237e810b695749ad3b0d5e086fda99cf56b", "parents": [ "a59e1f79f4e553b244957527e7a66f5cb2a618e7" ], "author": { "name": "David Disseldorp", "email": "ddiss@suse.de", "time": "Wed Apr 13 18:44:22 2022 +0200" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:08:39 2022 +0800" }, "message": "generic/020: fix max_attrval_size output filter\n\nThe current attr -g \"$max_attrval_name\" output filter is broken if\n$max_attrval_size isn\u0027t 16-byte aligned, due to od\u0027s duplicate\nsuppression behaviour.\nFix it by having od only dump one byte per line.\n\nSigned-off-by: David Disseldorp \u003cddiss@suse.de\u003e\nReviewed-by: Dave Chinner \u003cdchinner@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "a59e1f79f4e553b244957527e7a66f5cb2a618e7", "tree": "66a3dbe7f12b1025b3ecbf9149dee1b749b6b9e9", "parents": [ "dc76e4ec19a8e9da6366cf75d86e063409a385c1" ], "author": { "name": "David Disseldorp", "email": "ddiss@suse.de", "time": "Wed Apr 13 18:44:21 2022 +0200" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:08:31 2022 +0800" }, "message": "generic/020: fix max_attrval_size for XFS, UDF, Btrfs and NFS\n\nAs found by Dave Chinner, fff4359d (\"020: make this xattr test generic\")\nunintentionally changed the long attribute value length from 100K to 64\n*bytes* for XFS, UDF and Btrfs.\nUpdate XFS and UDF to use a 64K $max_attrval_size value. For Btrfs, use\nthe nodesize, xattr length and tree entry overhead sizes to calculate\nthe maximum.\nNFS doesn\u0027t provide a way to find out the $max_attrval_size for the\nunderlying filesystem on the server, so just use a rough 1K limit.\n\nSigned-off-by: David Disseldorp \u003cddiss@suse.de\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "dc76e4ec19a8e9da6366cf75d86e063409a385c1", "tree": "4ecfe4ea4ea16102bce92722ebce59e1d7aee8e1", "parents": [ "73aa648ce176f159f41538765be3392d3941d8e8" ], "author": { "name": "David Disseldorp", "email": "ddiss@suse.de", "time": "Wed Apr 13 18:44:20 2022 +0200" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:08:23 2022 +0800" }, "message": "generic/020: add and use _attr_get_max()\n\nIn preparation for taking into account the attr name length when\ncalculating $MAX_ATTRVAL_SIZE, put the current logic in a\n_attr_get_max() helper function and set local $max_attrval_size /\n$max_attrs variables instead of using export.\n\nSigned-off-by: David Disseldorp \u003cddiss@suse.de\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "73aa648ce176f159f41538765be3392d3941d8e8", "tree": "79ef3a52aa89abdad77d44831f229b1d47f21904", "parents": [ "c4cefb1c5ecd92f16fb14d82e8b6542e5fdbb535" ], "author": { "name": "David Disseldorp", "email": "ddiss@suse.de", "time": "Wed Apr 13 18:44:19 2022 +0200" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:08:04 2022 +0800" }, "message": "generic/020: move MAX_ATTRS and MAX_ATTRVAL_SIZE logic\n\nNo functional change. MAX_ATTRS and MAX_ATTRVAL_SIZE are only used\nwithin generic/020, so move the logic for determining these values\nover there.\n\nSigned-off-by: David Disseldorp \u003cddiss@suse.de\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "c4cefb1c5ecd92f16fb14d82e8b6542e5fdbb535", "tree": "fb7f910225fcb8c39912244575ead0598c2b7aca", "parents": [ "0b11a5ecb8e5ca8c2a9a5aa59c493a2d9fd485f8" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Mon Apr 11 15:08:38 2022 +0100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 20:01:13 2022 +0800" }, "message": "common/rc: fix _try_scratch_mount() and _test_mount() when mount fails\n\nAfter the recent commit 4a7b35d7a76cd9 (\"common: allow to run all tests\non idmapped mounts\"), some test that use _try_scratch_mount started to\nfail. For example:\n\n$ ./check btrfs/131 btrfs/220\nFSTYP -- btrfs\nPLATFORM -- Linux/x86_64 debian9 5.17.0-rc8-btrfs-next-114 (...)\nMKFS_OPTIONS -- /dev/sdc\nMOUNT_OPTIONS -- /dev/sdc /home/fdmanana/btrfs-tests/scratch_1\n\nbtrfs/131 2s ... - output mismatch (see .../results//btrfs/131.out.bad)\n --- tests/btrfs/131.out\t2020-06-10 19:29:03.818519162 +0100\n +++ /home/fdmanana/git/hub/xfstests/results//btrfs/131.out.bad (...)\n @@ -6,8 +6,6 @@\n Disabling free space cache and enabling free space tree\n free space tree is enabled\n Trying to mount without free space tree\n -mount failed\n -mount failed\n Mounting existing free space tree\n free space tree is enabled\n ...\n (Run \u0027diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/131.out ...\nbtrfs/220 7s ... - output mismatch (see .../results//btrfs/220.out.bad)\n --- tests/btrfs/220.out\t2020-10-16 23:13:46.802162554 +0100\n +++ /home/fdmanana/git/hub/xfstests/results//btrfs/220.out.bad (...)\n @@ -1,2 +1,32 @@\n QA output created by 220\n +Option fragment\u003dinvalid should fail to mount\n +umount: /home/fdmanana/btrfs-tests/scratch_1: not mounted.\n +Option nologreplay should fail to mount\n +umount: /home/fdmanana/btrfs-tests/scratch_1: not mounted.\n +Option norecovery should fail to mount\n +umount: /home/fdmanana/btrfs-tests/scratch_1: not mounted.\n ...\n (Run \u0027diff -u /home/fdmanana/git/hub/xfstests/tests/btrfs/220.out ...\nRan: btrfs/131 btrfs/220\nFailures: btrfs/131 btrfs/220\nFailed 2 of 2 tests\n\nThe reason is that if _try_scratch_mount() fails to mount the filesystem,\nwe don\u0027t return the failure, instead we call _idmapped_mount(), which\ncan succeed and make _try_scratch_mount() return 0 (success). The same\nhappens for _test_mount(), however a quick search revealed no tests\ncurrently relying on the return value of _test_mount().\n\nSo fix that by making _try_scratch_mount() return immediately if it gets\na mount failure. Also do the same for _test_mount().\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Dave Chinner \u003cdchinner@redhat.com\u003e\nAcked-by: Christian Brauner (Microsoft) \u003cbrauner@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "0b11a5ecb8e5ca8c2a9a5aa59c493a2d9fd485f8", "tree": "9f5040ec8452d616ca77594d753bf00792e506b8", "parents": [ "daa0c0146c7db84d1e368fcfcc8751566695b590" ], "author": { "name": "Zorro Lang", "email": "zlang@redhat.com", "time": "Tue Apr 12 00:37:10 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 19:56:22 2022 +0800" }, "message": "fstests: test dirty pipe vulnerability issue of CVE-2022-0847\n\nTest for the Dirty Pipe vulnerability (CVE-2022-0847) caused by an\nuninitialized \"pipe_buffer.flags\" variable. The bug cause a file\ncan be overwritten even if a user/process is not permitted to write\nit. It\u0027s fixed by 9d2231c5d74e (\"lib/iov_iter: initialize \"flags\" in\nnew pipe_buffer\").\n\nCc: Max Kellermann \u003cmax.kellermann@ionos.com\u003e\nSigned-off-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "daa0c0146c7db84d1e368fcfcc8751566695b590", "tree": "e69d9695e6f0624305f79d6b2cc634f96163bb3d", "parents": [ "4a7b35d7a76cd993ad7a62fd180e00589c73ac4b" ], "author": { "name": "Zorro Lang", "email": "zlang@redhat.com", "time": "Tue Apr 12 00:37:09 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 17 19:53:32 2022 +0800" }, "message": "fstests: replace hexdump with od command\n\nThe \"od\" is one of the most fundamental commands in GNU/Linux and\nmost Unix-like systems. So we nearly always can count on it, don\u0027t\nneed to check if it\u0027s installed.\n\nThe \"hexdump\" isn\u0027t such fundamental as \"od\", some systems don\u0027t\ninstall it by default. And as \"od\" nearly can replace all functions\nof \"hexdump\", so let\u0027s use an unified command \"od\" to do the hexdump\njob in fstests cases.\n\nSigned-off-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Dave Chinner \u003cdchinner@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "4a7b35d7a76cd993ad7a62fd180e00589c73ac4b", "tree": "76620e5bd8d4d1bcbd426a9cd4f52914355986b7", "parents": [ "09efb6c78d0f2ee03a59e3824d9e211332b9a711" ], "author": { "name": "Christian Brauner", "email": "brauner@kernel.org", "time": "Thu Apr 07 13:21:57 2022 +0200" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:52:36 2022 +0800" }, "message": "common: allow to run all tests on idmapped mounts\n\nIn addition to the generic and filesystem-specific idmapped mount\ntestsuites that already exist upstream today add simple\ninfrastructure so any test can be run on idmapped mounts simply by\nsetting IDMAPPED_MOUNTS\u003dtrue in the config file or section. The main\nuser for now will be overlay to verify it works correctly on\nidmapped mounts.\n\nNote that the infrastructure is completely generic so every\nfilesystem that supports idmapped mounts can simply run all of their\ntests idmapped. But note that not all ways to create a mount have\nbeen converted yet. That includes e.g. _dmthin_mount and direct\ncalls to _mount in various tests.\n\nIn addition, there will be corner-cases. For example, xfs doesn\u0027t\nallow bulkstat on idmapped mounts because it is a filesystem wide\noperation, i.e. you can retrieve information for any inode in the\nfilesystem so the operation cannot be scoped reasonably under a\nsingle mount. So xfstests testing bulkstat will fail as it\u0027s\nblocked. Similar for some btrfs ioctl()s.\n\nWhile we could of course restrict this testmode to -overlay for\nwhich we know things work correctly we should not do this. It would\nmean that people won\u0027t start using it and so we won\u0027t see issues\nunless someone sits down and goes through more than 1000 tests and\nfigures out for each individual one whether it needs to be skipped\nor not.\n\nSo instead allow this mode but for all filesystems so people can\nstart running and reporting failures and we can fix them up or block\nthem as we detect them.\n\nCc: Eryu Guan \u003cguaneryu@gmail.com\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\nCc: \u003cfstests@vger.kernel.org\u003e\nReviewed-by: Amir Goldstein \u003camir73il@gmail.com\u003e\nSigned-off-by: Christian Brauner (Microsoft) \u003cbrauner@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "09efb6c78d0f2ee03a59e3824d9e211332b9a711", "tree": "0fdff305f338992f722b0cb5a4d7a6a43c9b952c", "parents": [ "424acebff4fa2f99c5f3174787887d83e5481af7" ], "author": { "name": "Luís Henriques", "email": "lhenriques@suse.de", "time": "Tue Apr 05 10:46:33 2022 +0100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:44:24 2022 +0800" }, "message": "common/encrypt: allow the use of \u0027fscrypt:\u0027 as key prefix\n\nfscrypt keys have used the $FSTYP as prefix. However this format is being\ndeprecated and newer kernels are expected to use the generic \u0027fscrypt:\u0027\nprefix instead. This patch adds support for this new prefix, and only\nuses $FSTYP on filesystems that didn\u0027t initially supported it, i.e. ext4 and\nf2fs. This will allow old kernels to be tested.\n\nSigned-off-by: Luís Henriques \u003clhenriques@suse.de\u003e\nReviewed-by: Eric Biggers \u003cebiggers@google.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "424acebff4fa2f99c5f3174787887d83e5481af7", "tree": "50d7ab711a3f4d338a80d07f9b7608bf28e5a111", "parents": [ "24cf6fa013707d90612ba5478fb793d6069c0123" ], "author": { "name": "David Disseldorp", "email": "ddiss@suse.de", "time": "Wed Mar 30 13:45:40 2022 +0200" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:43:34 2022 +0800" }, "message": "btrfs: drop no-op count\u003d$(( count-- ))\n\nThis line doesn\u0027t result in a changed count value. The tests don\u0027t\nappear to rely on a decremented value, so remove the line.\n\nSigned-off-by: David Disseldorp \u003cddiss@suse.de\u003e\nReviewed-by: Anand Jain \u003canand.jain@oracle.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "24cf6fa013707d90612ba5478fb793d6069c0123", "tree": "8ba04f6746efd2c854b2d97909b1e792b0e88d0d", "parents": [ "9577dac5d24f5b57ae1c4fbb960ebac05a233063" ], "author": { "name": "Zorro Lang", "email": "zlang@redhat.com", "time": "Wed Mar 30 13:25:06 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:42:12 2022 +0800" }, "message": "fsx: remove XFS_IOC_ALLOCSP operation entirely\n\nDue to XFS_IOC_ALLOCSP is nearly retired from linux xfs, and the\nALLOCSP testing in fsx easily trigger errors. So compare with\ndisable it by default, I\u0027d like to remove it entirely. So this patch\nrevert two patches:\n\ncd99a499 (\"fsx: disable allocsp_calls if -F is specified\")\na32fb1bb (\"fsx: add support for XFS_IOC_ALLOCSP\")\n\nSigned-off-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "9577dac5d24f5b57ae1c4fbb960ebac05a233063", "tree": "31ff36bb1c353b4431901e69a8e7451c9d71da95", "parents": [ "a7e2b797f865831fcb883d15e06c2c17246caed8" ], "author": { "name": "Pankaj Raghav", "email": "p.raghav@samsung.com", "time": "Fri Mar 25 11:19:08 2022 +0100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:39:16 2022 +0800" }, "message": "btrfs/237: Use zone cap instead of zone size in fill_size and rest calculation\n\nThis test will break when zone capacity !\u003d zone size because the\ncalculation of the size to be filled is done using zone_size instead\nof the actual capacity available per zone. Fix it by using zone\ncapacity.\n\nAs a zoned device can have variable capacity, use the btrfs utility\nto get the zone capacity from the first data block group that the\ntest will be performed on.\n\nThe support to extract zone capacity was added to blkzone only from\nversion 2.37. So zcap will be used only when the blkzone version is\ngreater or equal to 2.37.\n\nSigned-off-by: Pankaj Raghav \u003cp.raghav@samsung.com\u003e\nReviewed-by: Naohiro Aota \u003cnaohiro.aota@wdc.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "a7e2b797f865831fcb883d15e06c2c17246caed8", "tree": "2b2f11bc398b465e1dd44c93c325a3f1ec3692a0", "parents": [ "1133ecda69f92cee3875b9f12fb4a1957d97aef1" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Tue Mar 08 21:18:49 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:36:04 2022 +0800" }, "message": "btrfs/194: allow it to be run on systems with page size larger than 4K\n\nSince btrfs has subpage support since v5.15, there is no need to\nrequire such hard requirement on 4K page size.\n\nWe only need to check if the current system support 4K as\nsectorsize.\n\nNow the test case can pass on aarch64 with 64K page size.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "1133ecda69f92cee3875b9f12fb4a1957d97aef1", "tree": "c52e4c216ee6ae061f337220e9cfbd91eedfd9df", "parents": [ "7834a74058c2543aa3d85465a5e52c9af7b2ab91" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Tue Mar 08 21:03:42 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:35:13 2022 +0800" }, "message": "common/btrfs: don\u0027t skip the test if BTRFS_PROFILE_CONFIGS contains unsupported profile\n\n[BUG]\nSometimes the tester wants to use $BTRFS_PROFILE_CONFIGS to limit the\ntests to certain profiles.\n\nThis is especially useful for btrfs subpage tests, as we don\u0027t yet\nsupport RAID56 for it yet.\n\nBut unfortunately, if we specify $BTRFS_PROFILE_CONFIGS with the\nfollowing content:\n\n export BTRFS_PROFILE_CONFIGS\u003d\"single:single dup:single raid0:raid0 \\\n\t\t\t raid1:raid1 raid10:raid10\"\n\nA lot of tests will not run, like:\n\n btrfs/064 30s ... [not run] Profile dup not supported for replace\n btrfs/065 26s ... [not run] Profile dup not supported for replace\n btrfs/066 27s ... 14s\n btrfs/069 25s ... [not run] Profile dup not supported for replace\n btrfs/070 59s ... [not run] Profile dup not supported for replace\n btrfs/071 25s ... [not run] Profile dup not supported for replace\n\n[CAUSE]\nThose test cases uses _btrfs_get_profile_configs() to grab the profiles\nwhich support given workload (like replace/repace-missing).\n\nBut _btrfs_get_profile_configs() will behave different based on whether\nBTRFS_PROFILE_CONFIGS is defined.\n\nIf not defined, it goes with default profiles, and just skip those\nunsupported.\nThis is what we want.\n\nBut if the environment variable is defined, it will not run if there is\nany unsupported profile in it.\n\n[FIX]\nUnify the behaivor by always skip the unsupported profiles, no matter if\n$BTRFS_PROFILE_CONFIGS is defined or not.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "7834a74058c2543aa3d85465a5e52c9af7b2ab91", "tree": "d7e4341414ef09a74acbd88d6a72f68126026255", "parents": [ "866948e00073fd7781f287e894918859ddb5f35e" ], "author": { "name": "Catherine Hoang", "email": "catherine.hoang@oracle.com", "time": "Thu Mar 17 23:24:08 2022 +0000" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:27:21 2022 +0800" }, "message": "xfs/019: extend protofile test\n\nThis test creates an xfs filesystem and verifies that the filesystem\nmatches what is specified by the protofile.\n\nThis patch extends the current test to check that a protofile can\nspecify setgid mode on directories. Also, check that the created\nsymlink isn’t broken.\n\nSigned-off-by: Catherine Hoang \u003ccatherine.hoang@oracle.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Allison Henderson \u003callison.henderson@oracle.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "866948e00073fd7781f287e894918859ddb5f35e", "tree": "edc8869b0b5f1b0dfb436eed94b9928e9488033a", "parents": [ "9e8dac56ff3089de7e345bdbfb547a0f2df53759" ], "author": { "name": "Josef Bacik", "email": "josef@toxicpanda.com", "time": "Thu Mar 24 16:24:34 2022 -0400" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:25:22 2022 +0800" }, "message": "btrfs/029: change the cross vfsmount reflink test\n\nWe now allow cross vfsmount reflinks, change this test to make sure\nwe pass the cross-vfsmount reflink.\n\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "9e8dac56ff3089de7e345bdbfb547a0f2df53759", "tree": "118f339eb53884946c89881c0212254f7019c954", "parents": [ "e030808c1774e88c6e919d1cfc8126aee3dff0cb" ], "author": { "name": "Josef Bacik", "email": "josef@toxicpanda.com", "time": "Thu Mar 24 16:24:33 2022 -0400" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:24:30 2022 +0800" }, "message": "generic/374: validate cross-vfsmount dedupe\n\nWe allow for cross-vfsmount dedupes now, change this test to\nvalidate dedupe works properly cross-vfsmount.\n\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Dave Chinner \u003cdchinner@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "e030808c1774e88c6e919d1cfc8126aee3dff0cb", "tree": "15e6bfbd089f6411dcc46ef04e1418cc5010ccb8", "parents": [ "7c9de12773d94c5c138976295a704dd8d31a188b" ], "author": { "name": "Josef Bacik", "email": "josef@toxicpanda.com", "time": "Thu Mar 24 16:24:32 2022 -0400" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:22:47 2022 +0800" }, "message": "generic/373: change test to validate cross-vfsmount reflink\n\nWe now allow cross-vfsmount reflinks so change the test to validate\nthat cross-vfsmount reflinks work.\n\nSigned-off-by: Josef Bacik \u003cjosef@toxicpanda.com\u003e\nReviewed-by: Dave Chinner \u003cdchinner@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "7c9de12773d94c5c138976295a704dd8d31a188b", "tree": "1c622ff98064938fb4a4bbdf0d682f8133987116", "parents": [ "d019cd411869e44b6880c09757de299729396e75" ], "author": { "name": "Boyang Xue", "email": "bxue@redhat.com", "time": "Wed Mar 30 14:03:39 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:21:38 2022 +0800" }, "message": "generic/674: replace _require_scratch_reflink with _require_scratch_dedupe\n\nSigned-off-by: Boyang Xue \u003cbxue@redhat.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "d019cd411869e44b6880c09757de299729396e75", "tree": "40368e5d10f98bf219b1f15ff151f2853984d6fd", "parents": [ "b5660918c9826f62934469b3b61d9e1c920288d3" ], "author": { "name": "Sun Ke", "email": "sunke32@huawei.com", "time": "Wed Mar 23 16:37:24 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:18:14 2022 +0800" }, "message": "generic/066: attr1 is still there after log replay on f2fs\n\nThe test fail on f2fs:\n xattr names and values after second fsync log replay:\n # file: SCRATCH_MNT/foobar\n +user.attr1\u003d\"val1\"\n user.attr3\u003d\"val3\"\n\nattr1 is still there after log replay. f2fs doesn\u0027t support fs-op level\ntransaction functionality. so it have no way to persist all metadata\nupdates in one transaction. We can use \"fastboot\" mountoption for this\ncase, so during last fsync on qwerty, f2fs can trigger a checkpoint\nwhich will persist all metadata updates before fsync().\n\nSuggested-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Sun Ke \u003csunke32@huawei.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "b5660918c9826f62934469b3b61d9e1c920288d3", "tree": "c4dcf32367e4f63aa002c1a2e58362685fad19e0", "parents": [ "513338e6a74342d5614c7a27b278f0195e42a12f" ], "author": { "name": "Dai Shili", "email": "daisl.fnst@fujitsu.com", "time": "Fri Mar 25 16:04:12 2022 -0400" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:16:44 2022 +0800" }, "message": "generic/631: use trusted.* extended attributes to filter NFS filesystem\n\nSince commit 2461e8901c (\"generic/631: Add a check for extended\nattributes\"), check of user.* extended attributes was added to avoid\nrunning this tests for filesystems that are not supported.\n\nBut it still fails on NFSv4.2 when mount overlayfs with the\nfollowing error.\n\n/var/mnt/scratch/merged0: wrong fs type, bad option, bad superblock\non overlay, missing codepage or helper program, or other error.\n\ndmesg log reports the following -\noverlayfs: upper fs does not support xattr, falling back to index\u003doff and metacopy\u003doff.\n\nAs per the linux patch series(https://lwn.net/Articles/799185/ ), the\nsupport of user extended attributes were added to NFSv4.2. So this\ncase passed the check of extended attributes by _require_attrs.\n\nAs per the overlayfs documentation -\n\n\"The upper filesystem will normally be writable and if it is it must\nsupport the creation of trusted.* and/or user.* extended attributes,\nand must provide valid d_type in readdir responses, so NFS is not\nsuitable.\"\n\nSo we can replace user.* extended attributes check with trusted.* to\nfilter NFS filesystem.\n\nSigned-off-by: Dai Shili \u003cdaisl.fnst@fujitsu.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "513338e6a74342d5614c7a27b278f0195e42a12f", "tree": "7e04e2458454dda1b5003a2fb21c7f1b9d28db1c", "parents": [ "52fe88c9f545f24670b12133e3941a9e0bafb929" ], "author": { "name": "Nitesh Shetty", "email": "nj.shetty@samsung.com", "time": "Wed Mar 23 23:36:43 2022 +0530" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 23:15:49 2022 +0800" }, "message": "generic/108: use blockdev utility to calculate physical and logical block size\n\nReading sysfs to get physical and logical block fails,\nif SCRATCH_DEV is partitioned device.\n\nSigned-off-by: Nitesh Shetty \u003cnj.shetty@samsung.com\u003e\nReported-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReported-by: Wang Yugui \u003cwangyugui@e16-tech.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "52fe88c9f545f24670b12133e3941a9e0bafb929", "tree": "a46417c59769c71d8ef69f29a641599774ffa7d1", "parents": [ "1e516c86003021861734a6b14628059316b1c455" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu Mar 17 16:34:32 2022 +0000" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 22:48:30 2022 +0800" }, "message": "generic: fallocate against a file range with a mix of holes and extents\n\nTest that if we call fallocate against a file range that has a mix\nof holes and written extents, the fallocate succeeds if the\nfilesystem has enough free space to allocate extents for the holes.\n\nThis test currently fails on btrfs and is fixed by a patch that has the\nfollowing subject:\n\n \"btrfs: only reserve the needed data space amount during fallocate\"\n\nThe test also fails on xfs, and after some discussion with Darrick,\nit seems it\u0027s due to technical reasons that would require a\nsignificant effort to xfs\u0027s implementation, and at the moment there\nisn\u0027t enough motivation to do such change. The relevent thread is at:\n\n https://lore.kernel.org/linux-btrfs/20220315164011.GF8241@magnolia/\n\nTherefore the test is intentionally skipped on xfs only. Ext4 and\nf2fs pass this test.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "1e516c86003021861734a6b14628059316b1c455", "tree": "5f30b31a311391611ef56c9fe4e89e2e01855dca", "parents": [ "775e2763a39264adba5c33482db89ef2b0634ac3" ], "author": { "name": "Eric Biggers", "email": "ebiggers@google.com", "time": "Sat Mar 12 17:05:59 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:40:55 2022 +0800" }, "message": "common/encrypt: verify the key identifiers\n\nAs part of all the ciphertext verification tests, verify that the\nfilesystem correctly computed the key identifier from the key the test\ngenerated. This uses fscrypt-crypt-util to compute the key identifier.\n\nPreviously this was only being tested indirectly, via the tests that\nhappen to use the hardcoded $TEST_RAW_KEY and $TEST_KEY_IDENTIFIER.\nThe new check provides better coverage.\n\nSigned-off-by: Eric Biggers \u003cebiggers@google.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "775e2763a39264adba5c33482db89ef2b0634ac3", "tree": "e40a39b517ddc20f9cbccbcc1b262a916fa5c483", "parents": [ "28eae4d04d1e82c90107fd7b1151cea72e8d79e7" ], "author": { "name": "Eric Biggers", "email": "ebiggers@google.com", "time": "Sat Mar 12 17:05:58 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:40:51 2022 +0800" }, "message": "common/encrypt: log full ciphertext verification params\n\nTo help with debugging, log some additional information to $seqres.full.\n\nSigned-off-by: Eric Biggers \u003cebiggers@google.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "28eae4d04d1e82c90107fd7b1151cea72e8d79e7", "tree": "5ed76c203d704b94342881e2a23867e75aacd755", "parents": [ "02222a33a0e59aac403b92a3e0dfb7953566b446" ], "author": { "name": "Eric Biggers", "email": "ebiggers@google.com", "time": "Sat Mar 12 17:05:57 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:40:48 2022 +0800" }, "message": "fscrypt-crypt-util: add support for dumping key identifier\n\nAdd an option to fscrypt-crypt-util to make it compute the key\nidentifier for the given key. This will allow testing the correctness\nof the filesystem\u0027s key identifier computation.\n\nSigned-off-by: Eric Biggers \u003cebiggers@google.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "02222a33a0e59aac403b92a3e0dfb7953566b446", "tree": "219575412887add82e4eba9fd2ee89bec311f7b4", "parents": [ "cd81e731261d0d062ad8ed8216deb51b110e4fd7" ], "author": { "name": "Eric Biggers", "email": "ebiggers@google.com", "time": "Sat Mar 12 17:05:56 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:40:44 2022 +0800" }, "message": "fscrypt-crypt-util: refactor get_key_and_iv()\n\nSplit get_key_and_iv() into two distinct parts: (1) deriving the key and\n(2) generating the IV. Also, check for the presence of needed options\njust before they are used rather than doing it all up-front.\n\nThese changes should make this code much easier to understand.\n\nSigned-off-by: Eric Biggers \u003cebiggers@google.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "cd81e731261d0d062ad8ed8216deb51b110e4fd7", "tree": "6239610391a125762ec4bc5a343ca45fcfbbfa59", "parents": [ "407ef6b96cc84758cc9791fd87703f2414907861" ], "author": { "name": "Eric Biggers", "email": "ebiggers@google.com", "time": "Sat Mar 12 17:05:55 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:40:39 2022 +0800" }, "message": "fscrypt-crypt-util: use an explicit --direct-key option\n\nMake fscrypt-crypt-util use an option --direct-key to specify the use of\nthe DIRECT_KEY method for key derivation and IV generation. Previously,\nthis method was implicitly detected via --mode-num being given without\neither --iv-ino-lblk-64 or --iv-ino-lblk-32, or --kdf\u003dnone being given\nin combination with --file-nonce.\n\nThe benefit of this change is that it makes the various options to\nfscrypt-crypt-util behave more consistently. --direct-key,\n--iv-ino-lblk-64, and --iv-ino-lblk-32 now all work similarly (they\nselect a key derivation and IV generation method); likewise, --mode-num,\n--file-nonce, --inode-number, and --fs-uuid now all work similarly (they\nprovide information that key derivation and IV generation may need).\n\nSigned-off-by: Eric Biggers \u003cebiggers@google.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "407ef6b96cc84758cc9791fd87703f2414907861", "tree": "f4814a06ac0fbbeb23d91100b19ae81694d44547", "parents": [ "4a21f002880a89a233512af21db3923c769e2250" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed Mar 16 15:13:26 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:37:13 2022 +0800" }, "message": "xfs/17[013]: fix intermittent failures when filesystem metadata gets large\n\nThese tests check that the filestreams allocator never shares an AG\nacross multiple streams when there\u0027s plenty of space in the filesystem.\nRecent increases in metadata overhead for newer features (e.g. bigger\nlogs due to reflink) can throw this off, so add another AG to the\nformatted filesystem to encourage it to avoid the AG with the log.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "4a21f002880a89a233512af21db3923c769e2250", "tree": "c4a52aa6a5e36dcc2911ab6090b8be7645a78c8c", "parents": [ "b3a59bb6dc16e26776f4c46e62f0381393068bfd" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed Mar 16 15:12:32 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:36:00 2022 +0800" }, "message": "xfs/076: only create files on the data device\n\nThis test checks that filesystems with sparse inode support can continue\nto allocate inodes when free space gets fragmented. Inodes only exist\non the data device, so we need to ensure that realtime is not enabled on\nthe filesystem so that the rt metadata doesn\u0027t mess with the inode usage\npercentage and cause a test failure.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "b3a59bb6dc16e26776f4c46e62f0381393068bfd", "tree": "f52a99ab5dc5cc162d73921e0256bcc4888ce32c", "parents": [ "bc593bd327e0c1e7ed67051d88c81fe3d09d9536" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Mar 15 20:30:25 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:34:25 2022 +0800" }, "message": "generic/673: fix golden output to reflect vfs setgid behavior\n\nFilipe Manana pointed out[1] that the setgid dropping behavior encoded\nin this generic test is based on some outdated XFS code, and not based\non what the VFS inode attribute change functions actually do. Now that\nwe\u0027re working on fixing that, we should update the golden output to\nreflect what all filesystems are supposed to be doing.\n\n[1] https://lore.kernel.org/linux-xfs/CAL3q7H47iNQ\u003dWmk83WcGB-KBJVOEtR9+qGczzCeXJ9Y2KCV25Q@mail.gmail.com/\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "bc593bd327e0c1e7ed67051d88c81fe3d09d9536", "tree": "9ccfd8873b3263e23d9c6a5c946bd769030e1215", "parents": [ "58331382174eaa8aedd72223906fb1265b450687" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Mar 15 20:30:20 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:33:04 2022 +0800" }, "message": "xfs/420: fix occasional test failures due to pagecache readahead\n\nEvery now and then, this test fails with this golden output:\n\n --- xfs/420.out\n +++ xfs/420.out.bad\n @@ -29,7 +29,7 @@\n Whence Result\n DATA 0\n HOLE 131072\n -DATA 196608\n +DATA 192512\n HOLE 262144\n Compare files\n c2803804acc9936eef8aab42c119bfac SCRATCH_MNT/test-420/file1\n\nCuriously, the file checksums always match, and it\u0027s not *forbidden* for\nthe page cache to have a page backing an unwritten extent that hasn\u0027t\nbeen written.\n\nThe condition that this test cares about is that block 3 (192k-256k) are\nreported by SEEK_DATA as data even if the data fork has a hole and the\nCOW fork has an unwritten extent. Matthew Wilcox thinks this is a side\neffect of readahead.\n\nTo fix this occasional false failure, call SEEK_DATA and SEEK_HOLE only\non the offsets that we care about.\n\nSuggested-by: Matthew Wilcox \u003cwilly@infradead.org\u003e\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "58331382174eaa8aedd72223906fb1265b450687", "tree": "05875989373fcb9218926388dd79738743d432f5", "parents": [ "e1b93b712f2993303cc5905efdb6c51b4fda7295" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Mar 15 20:30:14 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:31:01 2022 +0800" }, "message": "common/xfs: fix broken code in _check_xfs_filesystem\n\nFix some problems with undefined variables in the scrub control code.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "e1b93b712f2993303cc5905efdb6c51b4fda7295", "tree": "bbfa33439413267e36c3face61f32d308c8975b1", "parents": [ "cce62cbb35cdfab197ce7297c2997c3d460aaab2" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Mar 15 20:30:09 2022 -0700" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:29:28 2022 +0800" }, "message": "generic/459: ensure that the lvm devices have been created\n\nOnce in a /very/ long while this test fails because _mkfs_dev can\u0027t find\nthe LVM thinp volume after it\u0027s been created. Since the \"solution\" du\njour seems to be to sprinkle udevadm settle calls everywhere, do that\nhere in the hopes that will fix it.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "cce62cbb35cdfab197ce7297c2997c3d460aaab2", "tree": "bc2fac8cb4fa53608c8a12de6abc138932c12949", "parents": [ "4837b6aff4d3e466d3dfc3120fe4568ecf717180" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu Mar 03 11:36:42 2022 +0000" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 20:25:01 2022 +0800" }, "message": "generic: read multiple extents with io_uring\n\nTest doing a read, with io_uring, over a file range that includes\nmultiple extents. The read operation triggers page faults when\naccessing all pages of the read buffer except for the pages\ncorresponding to the first extent. We want to check that the\noperation results in reading all the extents and that it returns the\ncorrect data.\n\nThis is motivated by an issue found with MariaDB when using io_uring\nand running on btrfs. There\u0027s a patch for btrfs to address the issue\n\nca93e44bfb5f (\"btrfs: fallback to blocking mode when doing async dio\nover multiple extents\")\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "4837b6aff4d3e466d3dfc3120fe4568ecf717180", "tree": "c1a84c94058b323df97e5712092930fff564bf1d", "parents": [ "034e1a796f4b7bebd845ba66bf362d75ca02ef59" ], "author": { "name": "Masayoshi Mizuma", "email": "m.mizuma@jp.fujitsu.com", "time": "Wed Feb 16 09:55:20 2022 -0500" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 18:40:50 2022 +0800" }, "message": "xfs: test xfsdump with bind-mounted filesystem\n\ncommit 25195eb (\"xfsdump: handle bind mount target\") introduced\na bug of xfsdump which doesn\u0027t store the files to the dump file\ncorrectly when the root inode number is changed.\n\nThe commit 25195eb is reverted, and commit 0717c1c (\"xfsdump: intercept\nbind mount targets\") which is in xfsdump v3.1.10 fixes the bug to reject\nthe filesystem if it\u0027s bind-mounted.\n\nTest that xfsdump can reject the bind-mounted filesystem.\n\nSigned-off-by: Masayoshi Mizuma \u003cm.mizuma@jp.fujitsu.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "034e1a796f4b7bebd845ba66bf362d75ca02ef59", "tree": "475149f0b2899480eb659cfd104ceaee8e0c6c8c", "parents": [ "50490c851139599d18a60897ffd32e8dc16e1328" ], "author": { "name": "Ojaswin Mujoo", "email": "ojaswin@linux.ibm.com", "time": "Tue Feb 22 23:20:53 2022 +0530" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 18:32:20 2022 +0800" }, "message": "ext4: Test to ensure resize with sparse_super2 is handled correctly\n\nKernel currently doesn\u0027t support resize of EXT4 mounted with\nsparse_super2 option enabled. Earlier, it used to leave the resize\nincomplete and the fs would be left in an inconsistent state,\nhowever commit b1489186cc83[1] fixed this to avoid the fs corruption\nby clearly returning -EOPNOTSUPP.\n\nTest to ensure that kernel handles resizing with sparse_super2\ncorrectly. Run resize for multiple iterations because this sometimes\nleads to kernel crash due to fs corruption, which we want to detect.\n\nRelated commit in mainline:\n\n[1] commit b1489186cc8391e0c1e342f9fbc3eedf6b944c61\n\n\text4: add check to prevent attempting to resize an fs with sparse_super2\n\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "50490c851139599d18a60897ffd32e8dc16e1328", "tree": "19d2850e0bbbf5f529b5c9334a79e06484ea7049", "parents": [ "6c28307640211b57d4667ba8aafdaa686069cc46" ], "author": { "name": "Ojaswin Mujoo", "email": "ojaswin@linux.ibm.com", "time": "Tue Feb 22 23:20:52 2022 +0530" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Apr 10 18:28:21 2022 +0800" }, "message": "src/ext4_resize.c: Refactor code and ensure accurate errno is returned\n\nThe current implementation of ext4_resize returned 1 whenever\nthere was an error. Modify this to return the correct error code.\nThis is important for tests that rely on correct error reporting, by\nthe kernel, for ext4 resize functionality.\n\nAdditionaly, perform some code cleanup.\n\nSigned-off-by: Ojaswin Mujoo \u003cojaswin@linux.ibm.com\u003e\nReviewed-by: Ritesh Harjani \u003criteshh@linux.ibm.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "6c28307640211b57d4667ba8aafdaa686069cc46", "tree": "3f265bd06ddab8dca2e4f736d76b0bfd112c2e5d", "parents": [ "1ae79d2ecdac6f9ad94a660eca3d7586e34d7d6b" ], "author": { "name": "Andrey Albershteyn", "email": "aalbersh@redhat.com", "time": "Mon Mar 21 10:19:21 2022 +0100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Tue Mar 22 21:52:46 2022 +0800" }, "message": "README: restructure \u0026 format building manual\n\nThe commands for package managers for both Ubuntu and RHEL weren\u0027t\nup-to-date. A few packages doesn\u0027t exist anymore or missing from the\nlatest repositories (e.g. liburing-devel, btrfs-progs-devel).\nUbuntu\u0027s list missed a few packages listed in RHEL\u0027s list. There are\na few repeating steps. The indent of avaliable environment variables\nis not clear.\n\nThis patch:\n- Update package dependencies for Ubuntu/Debian/RHEL/CentOS/Fedora\n- Unify list of packages between Ubuntu/Debian and RHEL/CentOS/Fedora\n- Add list of tool packages for other FS\n- Add links to tools not in the standard repository for RHEL/CentOS\n- Drop xfsprogs-qa-devel reference for old systems\n- Replace note about EPEL with installation step with link to Fedora\n manual\n- Add configuration examples in \u0027Setup Environment\u0027\n- Small clarification details, such as size of the partition and\n KCONFIG_PATH description\n- Removal of repeating steps (install administrative tools,\n partitions content)\n- Restructuring and formatting of \"BUILDING THE FSQA SUITE\" section\n- Drop IRIXDEV references in variable set up\n- Variables in \u0027Additional setup\u0027 divided into groups\n- Move fsqa user/group creation and udf_test to \u0027Setup Environment\u0027\n section\n\nSigned-off-by: Andrey Albershteyn \u003caalbersh@redhat.com\u003e\nReviewed-by: Dave Chinner \u003cdchinner@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "1ae79d2ecdac6f9ad94a660eca3d7586e34d7d6b", "tree": "50b8a1463f2648483ec32b56a292eccdcc866108", "parents": [ "7fad8609aedb4640b8a09162a630f1a10707228e" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Tue Mar 15 20:00:20 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Mar 21 00:40:41 2022 +0800" }, "message": "btrfs: test that autdodefrag does not rewrite single extents\n\nThere is a report that btrfs autodefrag is defragging extents which\nonly have one single sector.\n\nSuch defragging will not reduce the number of extents, but only\nwaste IO.\n\nThe fix for it is titled:\n\n btrfs: avoid defragging extents whose next extents are not targets\n\nHere we add a test case, which will create an inode with the\nfollowing layout:\n\n 0 16K 20K 64K\n |\u003c-- Extent A --\u003e|\u003c-B-\u003e|\u003c----- Extent C ---\u003e|\n |Gen 7 |Gen 9|Gen 7 |\n\nAnd we trigger autodefrag with newer_than \u003d 8, which means it will\nonly defrag extents newer than or equal to generation 8.\n\nCurrently only Extent B meets the condition, but it can not be\nmerged with Extent A nor Extent C, as they don\u0027t meet the generation\nrequirement.\n\nUnpatched kernel will defrag only Extent B, resulting no change in\nfragmentation, while costs extra IO.\n\nPatched kernel will not defrag anything.\n\nAlthough this is still not the ideal case, as we can defrag the\nwhole 64K range, but that\u0027s not what autodefrag can do with its\ngeneration limitation.\n\nAnd such \"perfect\" defrag can cause way more IO than some users can\nstand.\n\nAt least we should not only defrag extent B.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "7fad8609aedb4640b8a09162a630f1a10707228e", "tree": "1037d7a4f3104b3d55d9212a43e167b7b064efaa", "parents": [ "cda30840132ba6e08e367c205cf563e0382d21dc" ], "author": { "name": "Shin\u0027ichiro Kawasaki", "email": "shinichiro.kawasaki@wdc.com", "time": "Tue Feb 22 13:19:08 2022 +0900" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Mar 21 00:38:41 2022 +0800" }, "message": "common/rc: avoid mixed mode for zoned btrfs\n\nWhen the helper function _scratch_mkfs_sized is called with small\nfilesystem size and FSTYP\u003dbtrfs, it calls mkfs.btrfs with --mixed option\nto enable mixed mode. However, mkfs.btrfs with --mixed option fails for\nzoned block devices since btrfs does not support mixed mode together\nwith zoned mode. To avoid this failure, do not set --mixed option when\nthe scratch device is a zoned block device.\n\nSigned-off-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nReviewed-by: Naohiro Aota \u003cnaohiro.aota@wdc.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "cda30840132ba6e08e367c205cf563e0382d21dc", "tree": "4d8d7b99d8d03c05a41360fba77e0d78567f0d2b", "parents": [ "0d2a65f3239b8de1811522385741523e6e6c3edc" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu Mar 03 11:40:21 2022 +0000" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Mar 21 00:26:40 2022 +0800" }, "message": "generic: move test case btrfs/261 into the generic group\n\nThe test case btrfs/261, part from its comments, doesn\u0027t really exercise\nany behaviour that is btrfs specific, so, as Dave Chinner pointed out, it\ncan be moved into the generic group.\n\nThis change moves that test into the generic group and slightly adjust the\ncomments to make it clear which parts are btrfs specific.\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "0d2a65f3239b8de1811522385741523e6e6c3edc", "tree": "bb76d170465809fcf4d994d24418f33c931c5b29", "parents": [ "e076938451cee0385fa8649c0e4630d4be261d71" ], "author": { "name": "Sidong Yang", "email": "realwakka@gmail.com", "time": "Wed Mar 02 14:05:48 2022 +0000" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Mar 21 00:25:00 2022 +0800" }, "message": "btrfs: add test for enable/disable quota and create/destroy qgroup repeatedly\n\nTest enable/disable quota and create/destroy qgroup repeatedly in\nparallel and confirm it does not cause kernel hang. It only happens\nin kernel staring with kernel 5.17-rc3. This is a regression test\nfor the problem reported to linux-btrfs list [1].\n\nThe hang was recreated using the test case and fixed by kernel patch\ntitled\n\n btrfs: qgroup: fix deadlock between rescan worker and remove qgroup\n\n[1] https://lore.kernel.org/linux-btrfs/20220228014340.21309-1-realwakka@gmail.com/\n\nSigned-off-by: Sidong Yang \u003crealwakka@gmail.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "e076938451cee0385fa8649c0e4630d4be261d71", "tree": "001a1a450f1726154c6d5a7b0a801cf983109937", "parents": [ "6d376c570228fb3cfc96a60e7cdfad3f70d98252" ], "author": { "name": "Nitesh Shetty", "email": "nj.shetty@samsung.com", "time": "Wed Mar 02 02:59:47 2022 +0530" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Mar 21 00:23:08 2022 +0800" }, "message": "generic/108: use sysfs values for logical,physical block size in scsi_debug\n\nscsi_debug device used for test, is created with assumption of 512\nbytes logical and physical block size.\n\nThis causes error in lvcreate step, when SCRATCH_DEV device lba is\nnot 512 bytes. This can be solved by reading block size from sysfs\nof device. If sysfs is missing fallback to 512 bytes as default.\n\nSigned-off-by: Nitesh Shetty \u003cnj.shetty@samsung.com\u003e\nReviewed-by: Luis Chamberlain \u003cmcgrof@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "6d376c570228fb3cfc96a60e7cdfad3f70d98252", "tree": "14eeae8602fc8204e23db51e9ac9d11f2e8586bb", "parents": [ "2ea74ba4e70b546279896e2a733c8c7f4b206193" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Tue Feb 22 11:36:58 2022 +0100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Mar 21 00:18:33 2022 +0800" }, "message": "generic: Add test for seekdir\n\nAdd test checking functionality of seekdir. We check whether seekdir\ngets us back to the directory entry it should and also whether\nseeking to random positions does not crash the filesystem.\n\nUnlike test generic/310 which also tests seeking, this test checks both\nglibc readdir() function as well as getdents64() syscall directly. This\nis because glibc readdir() implementation does a lot of caching and\nprocessing internally thus hiding kernel from some possible problems.\nAlso test wider range of random offsets to have better chance of\nhitting out of bound accesses or other bugs.\n\nThis is a regression test for a48fc69fe658 (\"udf: Fix crash after\nseekdir\")\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "2ea74ba4e70b546279896e2a733c8c7f4b206193", "tree": "db54facf340012ee4a8561396d766dd4ce477ecd", "parents": [ "41e691e469f7db212f2fc8b800706e16117ae761" ], "author": { "name": "Anthony Iliopoulos", "email": "ailiop@suse.com", "time": "Wed Feb 16 20:03:34 2022 +0100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 01:18:47 2022 +0800" }, "message": "btrfs: add support for capturing metadumps of corrupted fses\n\nAdd the capability to capture btrfs metadumps when filesystem checks\nfail, so that they can be used for further debugging. This is useful\nfor tests that _require_test and/or _require_scratch for which\nfilesystem checkers will run after a test completes and may\noccasionally pick up inconsistencies.\n\nSigned-off-by: Anthony Iliopoulos \u003cailiop@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "41e691e469f7db212f2fc8b800706e16117ae761", "tree": "35628f55c325fbe9a8da02e79e0f679277be2f00", "parents": [ "96b95682588f8e785579be57c80f5b1d5b2ed8ed" ], "author": { "name": "Filipe Manana", "email": "fdmanana@suse.com", "time": "Thu Feb 17 12:14:21 2022 +0000" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 01:08:59 2022 +0800" }, "message": "btrfs: log replay after fsync of file with prealloc extents beyond eof\n\nTest that after a full fsync of a file with preallocated extents\nbeyond the file\u0027s size, if a power failure happens, the preallocated\nextents still exist after we mount the filesystem.\n\nThis test currently fails and there is a patch for btrfs that fixes\nthis issue and has the following subject:\n\n \"btrfs: fix lost prealloc extents beyond eof after full fsync\"\n\nSigned-off-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "96b95682588f8e785579be57c80f5b1d5b2ed8ed", "tree": "24d1cf65e9fa4f22ae410d7ba50b9e05a159e20c", "parents": [ "1a7e6b57172d054823e7ea39110cf6dff1500065" ], "author": { "name": "Shin\u0027ichiro Kawasaki", "email": "shinichiro.kawasaki@wdc.com", "time": "Fri Feb 18 16:31:56 2022 +0900" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 01:01:49 2022 +0800" }, "message": "common: factor out xfs unique part from _filter_mkfs\n\nMost of the code in the function _filter_mkfs is xfs unique. This is\nmisleading that the function would be dedicated for xfs. Clean up the\nfunction by factoring out xfs unique part to _xfs_filter_mkfs in\ncommon/xfs. While at the same time, fix indent in _xfs_filter_mkfs to be\nconsistent with other functions in common/xfs.\n\nSuggested-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "1a7e6b57172d054823e7ea39110cf6dff1500065", "tree": "19951370b685c1957b08e96c9c86f311ebe40928", "parents": [ "ba2dedfb6ad7452da1378d216310932d8254e718" ], "author": { "name": "Shin\u0027ichiro Kawasaki", "email": "shinichiro.kawasaki@wdc.com", "time": "Fri Feb 18 16:31:55 2022 +0900" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 01:01:19 2022 +0800" }, "message": "xfs/015: check _scratch_mkfs_sized return code\n\nThe test cases xfs/015 calls _scratch_mkfs before _scratch_mkfs_sized,\nand does not check return code of _scratch_mkfs_sized. Even if\n_scratch_mkfs_sized failed, _scratch_mount after it cannot detect the\nsized mkfs failure because _scratch_mkfs already created a file system\non the device. This results in unexpected test condition.\n\nTo avoid the unexpected test condition, check return code of\n_scratch_mkfs_sized.\n\nSuggested-by: Naohiro Aota \u003cnaohiro.aota@wdc.com\u003e\nSigned-off-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "ba2dedfb6ad7452da1378d216310932d8254e718", "tree": "948f55ca8fbdad84d47a2fae8d91a41063c5cc21", "parents": [ "85a48b27b0e0f17a779426e43565e693e5e11bb7" ], "author": { "name": "Shin\u0027ichiro Kawasaki", "email": "shinichiro.kawasaki@wdc.com", "time": "Fri Feb 18 16:31:54 2022 +0900" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 01:01:14 2022 +0800" }, "message": "ext4/021: check _scratch_mkfs_sized return code\n\nThe test cases ext4/021 calls _scratch_mkfs before _scratch_mkfs_sized,\nand does not check return code of _scratch_mkfs_sized. Even if\n_scratch_mkfs_sized failed, _scratch_mount after it cannot detect the\nsized mkfs failure because _scratch_mkfs already created a file system\non the device. This results in unexpected test condition.\n\nTo avoid the unexpected test condition, check return code of\n_scratch_mkfs_sized.\n\nSuggested-by: Naohiro Aota \u003cnaohiro.aota@wdc.com\u003e\nSigned-off-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "85a48b27b0e0f17a779426e43565e693e5e11bb7", "tree": "7dab316a63c7846b685c7811df5818e695e73650", "parents": [ "3c47d5f0d091f4aa87fd6f5a0f65fade5c463a66" ], "author": { "name": "Shin\u0027ichiro Kawasaki", "email": "shinichiro.kawasaki@wdc.com", "time": "Fri Feb 18 16:31:53 2022 +0900" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 01:01:03 2022 +0800" }, "message": "generic/{171,172,173,174}: check _scratch_mkfs_sized return code\n\nThe test cases generic/{171,172,173,174} call _scratch_mkfs before\n_scratch_mkfs_sized, and they do not check return code of\n_scratch_mkfs_sized. Even if _scratch_mkfs_sized failed, _scratch_mount\nafter it cannot detect the sized mkfs failure because _scratch_mkfs\nalready created a file system on the device. This results in unexpected\ntest condition of the test cases.\n\nTo avoid the unexpected test condition, check return code of\n_scratch_mkfs_sized in the test cases.\n\nSuggested-by: Naohiro Aota \u003cnaohiro.aota@wdc.com\u003e\nSigned-off-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "3c47d5f0d091f4aa87fd6f5a0f65fade5c463a66", "tree": "ef9355c975e5bba6a36369d66e1be68eebe1f078", "parents": [ "67f9580c212dd1f2a8273f6194e686d187582255" ], "author": { "name": "Shin\u0027ichiro Kawasaki", "email": "shinichiro.kawasaki@wdc.com", "time": "Fri Feb 18 16:31:52 2022 +0900" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 01:00:29 2022 +0800" }, "message": "generic/204: remove unnecessary _scratch_mkfs call\n\nThe test case generic/204 calls _scratch_mkfs to get data block size and\ni-node size of the filesystem and obtained data block size is passed to\nthe following _scratch_mfks_sized call as an option. However, the\n_scratch_mkfs call is unnecessary since the sizes can be obtained by\n_scratch_mkfs_sized call without the data block size option.\n\nAlso the _scratch_mkfs call is harmful when the _scratch_mkfs succeeds\nand the _scratch_mkfs_sized fails. In this case, the _scratch_mkfs\nleaves valid working filesystem on scratch device then following mount\nand IO operations can not detect the failure of _scratch_mkfs_sized.\nThis results in the test case run with unexpected test condition.\n\nHence, remove the _scratch_mkfs call and the data block size option for\n_scratch_mkfs_sized call.\n\nSuggested-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Shin\u0027ichiro Kawasaki \u003cshinichiro.kawasaki@wdc.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "67f9580c212dd1f2a8273f6194e686d187582255", "tree": "0161200d96329ba5981bf04c24f6b58672f0f813", "parents": [ "9470dc5dddeaa48ef3633a46ab89523d78b3245f" ], "author": { "name": "Luis Chamberlain", "email": "mcgrof@kernel.org", "time": "Mon Feb 14 17:48:45 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 00:45:50 2022 +0800" }, "message": "tests/btrfs: use $AWK_PROG instead of awk\n\nUse $AWK_PROG instead of awk in case the default awk\nprogram is not called awk.\n\nSigned-off-by: Luis Chamberlain \u003cmcgrof@kernel.org\u003e\nReviewed-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nReviewed-by: Adam Manzanares \u003ca.manzanares@samsung.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "9470dc5dddeaa48ef3633a46ab89523d78b3245f", "tree": "1c480d1719ecfe67f1f5c5fe5d2814af25e45903", "parents": [ "115096a405bc82ca6c8b46c2c08ee1f7e77eb4b1" ], "author": { "name": "Luis Chamberlain", "email": "mcgrof@kernel.org", "time": "Mon Feb 14 17:48:44 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 00:44:51 2022 +0800" }, "message": "common/btrfs: use $AWK_PROG\n\nUse $AWK_PROG instead of just awk in case the preferred awk\nprogram is different.\n\nSigned-off-by: Luis Chamberlain \u003cmcgrof@kernel.org\u003e\nReviewed-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nReviewed-by: Adam Manzanares \u003ca.manzanares@samsung.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "115096a405bc82ca6c8b46c2c08ee1f7e77eb4b1", "tree": "139be6d031fdf6751236ede096af8724e1b5d077", "parents": [ "d01e8f25f31dd34c9c296099cf5dd35f13bb29e1" ], "author": { "name": "Luis Chamberlain", "email": "mcgrof@kernel.org", "time": "Mon Feb 14 17:48:43 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 00:43:07 2022 +0800" }, "message": "btrfs/237: adjust uuid heuristics\n\nUsing $(findmnt -n -o UUID mount-directory) only works on\nutil-linux v2.38, not on 2.37. Even debian-testing has util-linux\nv2.37, so use a mechanism which has worked for longer to fetch the\nUUID.\n\nWithout this the test fails on permission failure on accessing\nthe file /sys/fs/btrfs/\"$uuid\"/bg_reclaim_threshold as $uuid is\nempty. So while at it, add a check to ensure the UUID is never\nempty.\n\nUse $AWK_PROG in case the preferred awk program is not the\npreferred awk program.\n\nCc: Karel Zak \u003ckzak@redhat.com\u003e\nCc: Pankaj Raghav \u003cp.raghav@samsung.com\u003e\nSigned-off-by: Luis Chamberlain \u003cmcgrof@kernel.org\u003e\nReviewed-by: Johannes Thumshirn \u003cjohannes.thumshirn@wdc.com\u003e\nTested-by: Adam Manzanares \u003ca.manzanares@samsung.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "d01e8f25f31dd34c9c296099cf5dd35f13bb29e1", "tree": "f371cd8cffa211b42cff07ee9a7efb5188dcbbaf", "parents": [ "eb564a21879912c842a522aedef0fac6d922a467" ], "author": { "name": "Luis Chamberlain", "email": "mcgrof@kernel.org", "time": "Tue Feb 08 13:37:54 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 00:30:32 2022 +0800" }, "message": "common/config: fix use of MODPROBE_RM_PATIENT_TIMEOUT_ARGS\n\nWhen patient module removal support is detected on kmod\n(note that this is not yet even merged onto kmod yet but\nwork in progress) the arguments required for it are not being\nset yet. This was a typo, fix this.\n\nThis issue was spotted using shellcheck from blktests when adding\npatient module removal support there. I\u0027ll post a patch next to\nlet folks evaluate if we should embrace shellcheck on fstests as\nwell.\n\nSigned-off-by: Luis Chamberlain \u003cmcgrof@kernel.org\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "eb564a21879912c842a522aedef0fac6d922a467", "tree": "0f0d5fb98a4bcb19ae9f023d8726a71137af9a8d", "parents": [ "11342071e1054c65a28d32f3c6ab63c4bd6ef5a6" ], "author": { "name": "Sun Ke", "email": "sunke32@huawei.com", "time": "Tue Feb 08 15:16:24 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 21 00:01:07 2022 +0800" }, "message": "common/attr: adbjust acl_max of f2fs\n\nf2fs has set inline_xattr as a default option, and introduced a new\noption named \u0027noinline_xattr\u0027 for disabling default inline_xattr\noption. So in _acl_get_max we need to check \u0027noinline_xattr\u0027 string\nin fs option, otherwise we may select the wrong max acl number since\nwe always found the string \u0027inline_xattr\u0027 in fs option.\n\nAdditionally, f2fs has changed disk layout of xattr block a bit, so\nwill contain one more entry in both inline and noinline xattr inode,\nthis patch will modify the max acl number to adjust it.\n\nSuggested-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Sun Ke \u003csunke32@huawei.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "11342071e1054c65a28d32f3c6ab63c4bd6ef5a6", "tree": "3a1fd479a7b53729e30a3ce3e93faf23e17b1048", "parents": [ "b91862aa4c950e0157f241136207e3827cee407e" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Wed Feb 02 12:29:29 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Sun Feb 20 23:40:19 2022 +0800" }, "message": "src/fssum: use newer EVP_* interface to replace deprecated MD5_* interace\n\nIn OpenSSL 3.0, MD_Init/Update/Final() interfaces are marked\ndeprecated, and we have to go EVP_DigestInit/Update/Final() instead.\n\nPersonally I\u0027m not a fan of this, especially the new EVP_MD_CTX\nstructure can no longer be stack allocated, thus we have to\ndynamically allocate and free EVP_MD_CTX in sum_init() and sum_free().\n\nHopes this is proper way to go and would solve the problem until\nOpenSSL chooses to change their interface again.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "b91862aa4c950e0157f241136207e3827cee407e", "tree": "5bbb707c0e2de15f54861a6bc0c947477c93aee5", "parents": [ "bf49b2cde6d6a25d9174006bd7d443601fd97575" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Wed Feb 02 19:15:08 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 01:23:56 2022 +0800" }, "message": "btrfs: verify \"btrfs filesystem defragment -c\" behavior\n\nDespite the regular file defragging, \"btrfs filesystem defragment\"\nprovides an option, -c, to convert all data extents (except holes\nand preallocated ranges) to a new compression algorithm.\n\nThe special behavior here is, unlike regular defrag which is not\ngoing to touch extents which are adjacent to preallocated/hole\nranges, with -c, all non-hole/non-preallocated extents should be\ndefragged and converted to the new compression algorithm.\n\nThis test case will ensure the old behavior is properly kept.\n\nCurrently both old kernels (v5.15 and older) and newer kernel with\nrefactored defrag (v5.16 and newer) can pass the tests.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "bf49b2cde6d6a25d9174006bd7d443601fd97575", "tree": "3f35b85beb067ee35ffe6637a815a8d13a5f76b4", "parents": [ "8925b0290ffe0744d28f99a0a38e92e46cb85d75" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Fri Jan 28 08:27:01 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 01:19:34 2022 +0800" }, "message": "btrfs: defrag with compressed extents\n\nThere is a long existing bug in btrfs defrag code that it will\nalways try to defrag compressed extents, even they are already at\nmax capacity.\n\nThis will not reduce the number of extents, but only waste IO/CPU.\n\nThe kernel fix is titled:\n\n btrfs: defrag: don\u0027t defrag extents which is already at its max capacity\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "8925b0290ffe0744d28f99a0a38e92e46cb85d75", "tree": "878f142875ce86528bfef114d6b75d19877d617d", "parents": [ "d8639e1632ab3fe1d8044702699350ddf2499b12" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Fri Jan 28 08:27:00 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 01:17:46 2022 +0800" }, "message": "btrfs: autodefrag with regular and hole extents\n\nIn v5.11~v5.15 kernels, there is a regression in autodefrag that if\na cluster (up to 256K in size) has even a single hole, the whole\ncluster will be rejected.\n\nThis will greatly reduce the efficiency of autodefrag.\n\nThe behavior is fixed in v5.16 by a full rework, although the rework\nitself has other problems, it at least solves the problem.\n\nHere we add a test case to reproduce the case, where we have a 128K\ncluster, the first half is fragmented extents which can be\ndefragged. The second half is hole.\n\nMake sure autodefrag can defrag the 64K part.\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "d8639e1632ab3fe1d8044702699350ddf2499b12", "tree": "ac897faeb9d86cb083b3d64f0c9e3e9e787f1d9f", "parents": [ "cd99a4999bfb273319b6494c8e9497b063684059" ], "author": { "name": "Qu Wenruo", "email": "wqu@suse.com", "time": "Fri Jan 28 08:26:59 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 01:15:38 2022 +0800" }, "message": "btrfs: defrag with regular and preallocated extents\n\nRecent v5.16 has some regression around btrfs autodefrag mount\noption, and the extra scrutiny around defrag code exposes some\nquestionable behavior from the old code.\n\nOne behavior is to defrag extents along with the next preallocated\nextent.\n\nThis behavior will cause extra IO and convert all the preallocated\nextent to regular zero filled extents, rendering the preallocated\nextent useless.\n\nThe kernel fix is titled:\n\n btrfs: defrag: don\u0027t try to merge regular extents with preallocated extents\n\nSigned-off-by: Qu Wenruo \u003cwqu@suse.com\u003e\nReviewed-by: Filipe Manana \u003cfdmanana@suse.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "cd99a4999bfb273319b6494c8e9497b063684059", "tree": "f68877957528a9468816ffba1fc65e703dc7a054", "parents": [ "394c20991779de09e6fb1b60aa5c9eab1dfc9549" ], "author": { "name": "Zorro Lang", "email": "zlang@redhat.com", "time": "Sat Jan 29 12:44:31 2022 +0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 01:10:47 2022 +0800" }, "message": "fsx: disable allocsp_calls if -F is specified\n\nAs the fsx.c source code says:\n int fallocate_calls \u003d 1; /* -F flag disables */\n int allocsp_calls \u003d 1; /* -F flag disables */\n\nThe allocsp_calls and fallocate_calls should be disabled, if the -F\noption is specified. But current fsx forgets to disable allocsp_calls\nas is documented.\n\nSigned-off-by: Zorro Lang \u003czlang@redhat.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "394c20991779de09e6fb1b60aa5c9eab1dfc9549", "tree": "f571b50a9b70a974431c21f996c45ead7f43eff2", "parents": [ "a245d8b8158425f8f54dfc2d3bd4c601ede07b23" ], "author": { "name": "Lukas Czerner", "email": "lczerner@redhat.com", "time": "Tue Nov 23 11:11:19 2021 +0100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 01:09:22 2022 +0800" }, "message": "common/rc: set maximum label length for ext4\n\nSet maximum label length for ext4 in _label_get_max() to be able to test\nonline file system label set/get ioctls.\n\nSigned-off-by: Lukas Czerner \u003clczerner@redhat.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "a245d8b8158425f8f54dfc2d3bd4c601ede07b23", "tree": "329ea24de713feaa313e2fe5e4d526f90e7f13a5", "parents": [ "ccbbd09981c762d865a5198f6fe31b2f07bbc274" ], "author": { "name": "Dave Chinner", "email": "dchinner@redhat.com", "time": "Wed Feb 02 18:38:31 2022 +1100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 01:08:15 2022 +0800" }, "message": "fstests: add more tests to the metadump group\n\nBecause they use metadump and I want to test metadump more easily.\n\nSigned-off-by: Dave Chinner \u003cdchinner@redhat.com\u003e\nReviewed-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "ccbbd09981c762d865a5198f6fe31b2f07bbc274", "tree": "d125e533739891b2f1a30405bf238764577f6d44", "parents": [ "290e6c83e8d8232a98c0bf154ea3c6d7e7a09b0d" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Feb 01 18:19:36 2022 -0500" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 01:07:19 2022 +0800" }, "message": "common: handle old versions of modprobe which don\u0027t support --help\n\nThere exists versions of modprobe out there which are so old that\nmodprobe --help isn\u0027t a thing. They\u0027re certainly not going to support\nmodprobe --remove-patiently, so test to make sure modprobe --help\nworks to avoid causing all tests to fail due to the error message\nto stderr showing up in $seq.out.\n\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\nFixes: 405c21d40aa1 (\"common/module: add patient module rmmod support\")\nReported-by: Leah Rumancik \u003cleah.rumancik@gmail.com\u003e\nCc: Luis Chamberlain \u003cmcgrof@kernel.org\u003e\nReviewed-by: Luis Chamberlain \u003cmcgrof@kernel.org\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "290e6c83e8d8232a98c0bf154ea3c6d7e7a09b0d", "tree": "578230743422126871a9456f3da681fa405c5169", "parents": [ "705d9aff1d287ba3b65f6deee8ff9e1e1ff9617a" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Tue Jan 25 18:11:54 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 01:02:36 2022 +0800" }, "message": "fstests: skip tests that require XFS_IOC_ALLOCSP\n\nDeprecating this, so turn off the tests that require it.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Zorro Lang \u003czlang@redhat.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "705d9aff1d287ba3b65f6deee8ff9e1e1ff9617a", "tree": "da82d85165dbf15f5948f82c8f8eb332d5e9b8f3", "parents": [ "9017f3b63b50f467daf8a816f98dfc13544cdb49" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Wed Jan 26 17:27:01 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 00:53:30 2022 +0800" }, "message": "generic: test suid/sgid behavior with reflink and dedupe\n\nMake sure that we drop the setuid and setgid bits any time reflink or\ndedupe change the file contents.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "9017f3b63b50f467daf8a816f98dfc13544cdb49", "tree": "1f106dbe79bc739f457a2bb786ba1c68dffc0260", "parents": [ "6bd65c707208afdc3d81d3146ac171d7621c26ee" ], "author": { "name": "Anthony Iliopoulos", "email": "ailiop@suse.com", "time": "Fri Jan 21 14:58:02 2022 +0100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 00:40:57 2022 +0800" }, "message": "common/dump: add explicit requirement for specific users and groups\n\nMake the requirement for daemon:sys and bin:bin explicit, so that the\nxfs tests that source common/dump and rely on _do_create_dumpdir_fill\nand _create_dumpdir_symlinks do not fail on chown when those\nusers/groups are missing.\n\nSigned-off-by: Anthony Iliopoulos \u003cailiop@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "6bd65c707208afdc3d81d3146ac171d7621c26ee", "tree": "10dc22152b73b00c9c37f2329d3ce5ab1a61df57", "parents": [ "67f35c96a2d181b5b44ef9dfac309518dff7bb66" ], "author": { "name": "Anthony Iliopoulos", "email": "ailiop@suse.com", "time": "Fri Jan 21 14:58:01 2022 +0100" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Mon Feb 14 00:39:28 2022 +0800" }, "message": "common/rc: fix group detection regex to strictly match required name\n\n_require_group greps for the required group string in /etc/group but\nthis can partially match other groups or group member names and falsely\nreturn success where it should fail.\n\nMake the regex more specific so that it can unambigiously match only the\nexact group name rather than any other group that happens to match as a\nsubstring or any matching username from the group member list field.\n\nSigned-off-by: Anthony Iliopoulos \u003cailiop@suse.com\u003e\nReviewed-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" }, { "commit": "67f35c96a2d181b5b44ef9dfac309518dff7bb66", "tree": "2cc7c82fdcf18e2397b33c625fb1bb9256142ceb", "parents": [ "d8dee1222ecdfa1cff1386a61248e587eb3b275d" ], "author": { "name": "Darrick J. Wong", "email": "djwong@kernel.org", "time": "Mon Jan 24 10:37:35 2022 -0800" }, "committer": { "name": "Eryu Guan", "email": "guaneryu@gmail.com", "time": "Tue Jan 25 23:54:15 2022 +0800" }, "message": "generic/273: use _get_file_block_size\n\nThis test calculates the amount of free space on a filesystem and uses\nthe block size to spread the work of filling the free space among a\nbunch of threads. Unfortunately, the test /should/ be using the\nallocation unit size, not the fs block size, which is why this test\nfails on configurations such as XFS realtime with a 28k extent size.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@kernel.org\u003e\nReviewed-by: Leah Rumancik \u003cleah.rumancik@gmail.com\u003e\nSigned-off-by: Eryu Guan \u003cguaneryu@gmail.com\u003e\n" } ], "next": "d8dee1222ecdfa1cff1386a61248e587eb3b275d" }