On 22/08/2025 09:02, Ojaswin Mujoo wrote:
This adds atomic write test using fio based on it's crc check verifier. fio adds a crc header for each data block, which is verified later to ensure there is no data corruption or torn write. This test essentially does a lot of parallel RWF_ATOMIC IO on a preallocated file to stress the write and end-io unwritten conversion code paths. The idea is to increase code coverage to ensure RWF_ATOMIC hasn't introduced any issues. Avoid doing overlapping parallel atomic writes because it might give unexpected results. Use offset_increment=, size= fio options to achieve this behavior. Co-developed-by: Ritesh Harjani (IBM)<ritesh.list@xxxxxxxxx> Signed-off-by: Ritesh Harjani (IBM)<ritesh.list@xxxxxxxxx> Reviewed-by: Darrick J. Wong<djwong@xxxxxxxxxx> Signed-off-by: Ojaswin Mujoo<ojaswin@xxxxxxxxxxxxx>
I am still a bit skeptical of the value of this test, but here is my tag anyway:
Reviewed-by: John Garry <john.g.garry@xxxxxxxxxx>
