| commit | 4ba66134744885e676167dede2f5900512834a31 | [log] [tgz] |
|---|---|---|
| author | Jens Axboe <jens.axboe@oracle.com> | Tue Feb 05 10:05:50 2008 +0100 |
| committer | Jens Axboe <jens.axboe@oracle.com> | Tue Feb 05 10:05:50 2008 +0100 |
| tree | e99aab575d399926629786b136fab9dd22093629 | |
| parent | 97e8cd444561ef03dd65c6c3c37c934796a4993f [diff] |
Fix offset retrieval problem for read and write having different bs ranges "Zhang, Yanmin" <yanmin_zhang@linux.intel.com> reported that fio got stuck with a job file that had different read and write block size ranges. The problem is that get_next_offset() didn't take the data direction into account, so when it generated an offset close to the end of the file, it may not have been legal for that data direction. Signed-off-by: Jens Axboe <jens.axboe@oracle.com>