[PATCH 0/2] Fix job completion failure for sequential IOs with holes

From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: Damien Le Moal <Damien.LeMoal@wdc.com>,
	Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
	Niklas Cassel <niklas.cassel@wdc.com>,
	Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: [PATCH 0/2] Fix job completion failure for sequential IOs with holes
Date: Fri,  1 Oct 2021 19:32:55 +0900	[thread overview]
Message-ID: <20211001103257.4130231-1-shinichiro.kawasaki@wdc.com> (raw)

Commit 499cded5f435 ("Fix for loop count issue when do_verify=0 (#1093)")
triggered the failure of test case #7 of t/run-fio-tests.py. The test case
runs sequential read workload with holes and checks amount of read data. The
commit affected job completion condition, and resulted in unexpected larger
read data and the test case failure.

This series has two patches to address the issue. The first patch reverts the
commit, and the second patch proposes different fix for the loop count issue
with do_verify=0 option. I used the workload recorded in github issue #1093 to
confirm this second patch fixes the loop count issue.

Shin'ichiro Kawasaki (2):
  Revert "Fix for loop count issue when do_verify=0 (#1093)"
  Refer td->loops instead of td->o.loops to fix loop count issue

 backend.c | 4 ++--
 libfio.c  | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
2.31.1