diff options
| author | Sagi Grimberg <[email protected]> | 2021-01-13 13:56:57 -0800 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2021-01-14 20:27:35 +0100 |
| commit | ca1ff67d0fb14f39cf0cc5102b1fbcc3b14f6fb9 (patch) | |
| tree | 6e7c8cea04747d3c8efc190e8eb3175cc7ee894e /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | ada831772188192243f9ea437c46e37e97a5975d (diff) | |
nvme-tcp: fix possible data corruption with bio merges
When a bio merges, we can get a request that spans multiple
bios, and the overall request payload size is the sum of
all bios. When we calculate how much we need to send
from the existing bio (and bvec), we did not take into
account the iov_iter byte count cap.
Since multipage bvecs support, bvecs can split in the middle
which means that when we account for the last bvec send we
should also take the iov_iter byte count cap as it might be
lower than the last bvec size.
Reported-by: Hao Wang <[email protected]>
Fixes: 3f2304f8c6d6 ("nvme-tcp: add NVMe over TCP host driver")
Tested-by: Hao Wang <[email protected]>
Signed-off-by: Sagi Grimberg <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions