Searched hist:efcfec579f6139528c9e6925eca2bc4a36da65c6 (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/drivers/block/ |
| H A D | loop.c | diff efcfec579f6139528c9e6925eca2bc4a36da65c6 Wed Oct 30 22:29:48 CDT 2019 Darrick J. Wong <darrick.wong@oracle.com> loop: fix no-unmap write-zeroes request behavior
Currently, if the loop device receives a WRITE_ZEROES request, it asks
the underlying filesystem to punch out the range. This behavior is
correct if unmapping is allowed. However, a NOUNMAP request means that
the caller doesn't want us to free the storage backing the range, so
punching out the range is incorrect behavior.
To satisfy a NOUNMAP | WRITE_ZEROES request, loop should ask the
underlying filesystem to FALLOC_FL_ZERO_RANGE, which is (according to
the fallocate documentation) required to ensure that the entire range is
backed by real storage, which suffices for our purposes.
Fixes: 19372e2769179dd ("loop: implement REQ_OP_WRITE_ZEROES")
Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
|