Tomasz Zawadzki ccdbd2ed51 nvme/cuse: fix nblocks and block_size in rw path ... nblocks is zero based, so read path was missing the increment. NVMe device that cuse represents can be of any block_size, so rather than hardcoding 512 - actually verify it. Both paths didn't request enough of a buffer from cuse. Reported-by: Niklas Cassel Signed-off-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com> Change-Id: I228dc2572bc94ecbcb913e950d912a7ab5be9434 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/4037 Community-CI: Broadcom CI Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com>		2020-09-04 08:13:56 +00:00
..
.gitignore	test/nvme: dynamic nvme cuse devices update test	2020-06-05 09:01:44 +00:00
cuse.c	test/nvme: dynamic nvme cuse devices update test	2020-06-05 09:01:44 +00:00
Makefile	test/nvme: dynamic nvme cuse devices update test	2020-06-05 09:01:44 +00:00
nvme_cuse_rpc.sh	test/cuse: remove superfluous setup.sh	2020-06-17 07:20:55 +00:00
nvme_cuse.sh	test/cuse: run namespace managment test if device supports it	2020-06-17 07:20:55 +00:00
nvme_ns_manage_cuse.sh	test/cuse: use 512B block size on namespace revert	2020-06-23 08:04:05 +00:00
spdk_nvme_cli_cuse.sh	nvme/cuse: fix nblocks and block_size in rw path	2020-09-04 08:13:56 +00:00
spdk_smartctl_cuse.sh	test/common: add get_nvme_ctrlr_from_bdf()	2020-06-17 07:20:55 +00:00