You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In cases where worker completes specified number of `iterations` before
oper completes all `total_ios`, such oper remains on active_list.
This is a problem because cleanup only walks over finished list,
and closes fds only for items on this list. So it's possible for
test to exhaust ulimit for open files and fail:
$ ./aio-stress -a1 -I100 -o2 -r4 -f1 -d1^
aio-stress.c:1347: TPASS: Test passed
aio-stress.c:1285: TINFO: starting with random write
aio-stress.c:1296: TINFO: file size 1024MB, record size 0KB, depth 1, I/O per iteration 1
aio-stress.c:1298: TINFO: max io_submit 1, buffer alignment set to 4KB
aio-stress.c:1300: TINFO: threads 1 files 1 contexts 1 context offset 2MB verification off
aio-stress.c:1314: TBROK: open(file0.bin,1052738,0600) failed: EMFILE (24)
Clean/free also items from active_list. Also don't let `status` from cleanup
be set to zero once it becomes non-zero.
Signed-off-by: Jan Stancek <jstancek@redhat.com>
Acked-by: Andrea Cervesato <andrea.cervesato@suse.com>
Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
0 commit comments