mirror_zfs/tests/zfs-tests/cmd/file
Rich Ercolani b657f2c592
Corrected oversight in ZERO_RANGE behavior
It turns out, no, in fact, ZERO_RANGE and PUNCH_HOLE do
have differing semantics in some ways - in particular,
one requires KEEP_SIZE, and the other does not.

Also added a zero-range test to catch this, corrected a flaw
that made the punch-hole test succeed vacuously, and a typo
in file_write.

Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Rich Ercolani <rincebrain@gmail.com>
Closes #13329 
Closes #13338
2022-04-20 16:07:03 -07:00
..
file_check.c tests: cmd: don't recurse 2022-04-01 17:58:23 -07:00
file_common.h tests: cmd: don't recurse 2022-04-01 17:58:23 -07:00
file_trunc.c tests: cmd: don't recurse 2022-04-01 17:58:23 -07:00
file_write.c Corrected oversight in ZERO_RANGE behavior 2022-04-20 16:07:03 -07:00
largest_file.c tests: cmd: don't recurse 2022-04-01 17:58:23 -07:00
randfree_file.c tests: cmd: don't recurse 2022-04-01 17:58:23 -07:00
randwritecomp.c tests: cmd: don't recurse 2022-04-01 17:58:23 -07:00