Fix :<nr> suffix with random read/write causing 0 initial offset
authoraggieNick02 <nick@pcpartpicker.com>
Tue, 15 Feb 2022 17:59:34 +0000 (11:59 -0600)
committeraggieNick02 <nick@pcpartpicker.com>
Tue, 15 Feb 2022 20:43:41 +0000 (14:43 -0600)
commit54833d02a6ac307a894ed4445db9fe25e530b518
tree226358caabc992425fc6693ee90dc22a13cd4660
parentb832240d981b2c0addb5d90490ee493429f6bfda
Fix :<nr> suffix with random read/write causing 0 initial offset

When using the :<nr> suffix with random reads or writes, the initial
offset would be set to 0 for the first nr-1 operations. This happened
because td->ddir_seq_nr was initialized to the specified option value,
when it needs to always be initialized to 1, so that the first call to
get_next_offset leads to choosing a new random offset for the first nr
operations.

Signed-off-by: Nick Neumann nick@pcpartpicker.com
init.c