Zorro Lang e37418a588 fsstress: avoid splice_f generating too large sparse file ...

Thanks to Darrick J. Wong find this issue! Current splice_f generates
file offset as below:

  lr = ((int64_t)random() << 32) + random();
  off2 = (off64_t)(lr % maxfsize);

It generates a pseudorandom 64-bit candidate offset for the
destination file where we'll land the splice data, and then caps the
offset at maxfsize (which is 2^63- 1 on x64), which effectively means
that the data will appear at a very high file offset which creates
large (sparse) files very quickly.

That's not what we want, and some case likes shared/009 will take
forever to run md5sum on lots of huge files.

Signed-off-by: Zorro Lang <zlang@redhat.com>
Reviewed-by: Eryu Guan <guaneryu@gmail.com>
Signed-off-by: Eryu Guan <guaneryu@gmail.com>

2019-02-10 17:14:08 +08:00

..

aio-stress.c

ltp/: spdx license conversion

2018-06-22 10:38:11 +08:00

doio.c

ltp/: spdx license conversion

2018-06-22 10:38:11 +08:00

doio.h

ltp/: spdx license conversion

2018-06-22 10:38:11 +08:00

fsstress.c

fsstress: avoid splice_f generating too large sparse file

2019-02-10 17:14:08 +08:00

fsx.c

fsx: check ENOSYS in test_copy_range() & test_fallocate()

2019-01-06 22:02:53 +08:00

growfiles.c

ltp/: spdx license conversion

2018-06-22 10:38:11 +08:00

iogen.c

ltp/: spdx license conversion

2018-06-22 10:38:11 +08:00

Makefile

fsstress: add copy_file_range support

2018-12-09 22:55:47 +08:00

rwtest.sh

tests: remove IRIX support from tests also supported on Linux

2017-07-24 12:34:41 +08:00