Improve the fallocate() EINVAL in handle_aiocb_write_zeroes()

[PATCH 0/2] Improve the fallocate() EINVAL in handle_aiocb_write_zeroes()

Thomas Huth posted 2 patches 2 years, 11 months ago

Download series mbox

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/next-importer-push tags/patchew/20210527172020.847617-1-thuth@redhat.com

Maintainers: Max Reitz <mreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>

block/file-posix.c | 28 +++++++++++++++++++---------
1 file changed, 19 insertions(+), 9 deletions(-)

Expand all Fold all

[PATCH 0/2] Improve the fallocate() EINVAL in handle_aiocb_write_zeroes()

Posted by Thomas Huth 2 years, 11 months ago

On buggy file systems, fallocate() can return EINVAL for unaligned accesses.
Improve the situation by ignoring this for PUNCH_HOLE, too (but we also
print out an error message in this case now, since PUNCH_HOLE should really
never return EINVAL according to the man page). The second patch reworks
the handling for ZERO_RANGE a little bit so that we now also try the other
fallbacks in this case now.

Thomas Huth (2):
  block/file-posix: Fix problem with fallocate(PUNCH_HOLE) on GPFS
  block/file-posix: Try other fallbacks after invalid
    FALLOC_FL_ZERO_RANGE

 block/file-posix.c | 28 +++++++++++++++++++---------
 1 file changed, 19 insertions(+), 9 deletions(-)

-- 
2.27.0