On 8/10/24 15:18, Filipe Manana wrote: >>> There's also nothing in this test that is btrfs specific, it could be >>> made a generic test instead. >> >> Yes there is, it's running btrfs check every time. > > Right, but instead of calling it explicitly, it could pass > "_check_scratch_fs" as an argument instead, and the test becomes > generic: > > _log_writes_fast_replay_check fua "$SCRATCH_DEV" "_check_scratch_fs" Well, we could, but this is a test for a btrfs-specific race that existed between two known commits - this isn't a generic stress test. There's no reason to believe a) that other filesystems are vulnerable to this, or b) that their check programs would even pick it up. Mark
