summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2019-05-21 09:01:41 +0200
committerJens Axboe <axboe@kernel.dk>2019-05-23 10:25:26 -0600
commit09324d32d2a0843e66652a087da6f77924358e62 (patch)
tree9d7851cb620f46b7d7564b8fe18ccd2b22f74a8a /crypto
parenteded341c085bebdd653f8086c02179098cb81748 (diff)
downloadblackbird-op-linux-09324d32d2a0843e66652a087da6f77924358e62.tar.gz
blackbird-op-linux-09324d32d2a0843e66652a087da6f77924358e62.zip
block: force an unlimited segment size on queues with a virt boundary
We currently fail to update the front/back segment size in the bio when deciding to allow an otherwise gappy segement to a device with a virt boundary. The reason why this did not cause problems is that devices with a virt boundary fundamentally don't use segments as we know it and thus don't care. Make that assumption formal by forcing an unlimited segement size in this case. Fixes: f6970f83ef79 ("block: don't check if adjacent bvecs in one bio can be mergeable") Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Ming Lei <ming.lei@redhat.com> Reviewed-by: Hannes Reinecke <hare@suse.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud