aboutsummaryrefslogtreecommitdiff
path: root/Documentation/block
diff options
context:
space:
mode:
authorGravatar Pavel Begunkov <asml.silence@gmail.com> 2021-01-09 16:02:58 +0000
committerGravatar Jens Axboe <axboe@kernel.dk> 2021-01-25 08:58:24 -0700
commit9b2e0016d04c6542ace0128eb82ecb3b10c97e43 (patch)
tree7354e1e1321f6b8e1117fc77eb49f2c504006fee /Documentation/block
parentsplice: don't generate zero-len segement bvecs (diff)
downloadlinux-9b2e0016d04c6542ace0128eb82ecb3b10c97e43.tar.gz
linux-9b2e0016d04c6542ace0128eb82ecb3b10c97e43.tar.bz2
linux-9b2e0016d04c6542ace0128eb82ecb3b10c97e43.zip
bvec/iter: disallow zero-length segment bvecs
zero-length bvec segments are allowed in general, but not handled by bio and down the block layer so filtered out. This inconsistency may be confusing and prevent from optimisations. As zero-length segments are useless and places that were generating them are patched, declare them not allowed. Reviewed-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com> Reviewed-by: Ming Lei <ming.lei@redhat.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'Documentation/block')
-rw-r--r--Documentation/block/biovecs.rst2
1 files changed, 2 insertions, 0 deletions
diff --git a/Documentation/block/biovecs.rst b/Documentation/block/biovecs.rst
index 36771a131b56..ddb867e0185b 100644
--- a/Documentation/block/biovecs.rst
+++ b/Documentation/block/biovecs.rst
@@ -40,6 +40,8 @@ normal code doesn't have to deal with bi_bvec_done.
There is a lower level advance function - bvec_iter_advance() - which takes
a pointer to a biovec, not a bio; this is used by the bio integrity code.
+As of 5.12 bvec segments with zero bv_len are not supported.
+
What's all this get us?
=======================