Konrad Sztyber 5088a8930d nvme/tcp: check PDU type before checking padding ... Not all PDUs that have can have data can also have padding - e.g. C2HTermReq has data, but cannot have padding and the PDO field should be reserved. Therefore, for these PDUs the data starts exactly at the end of the header (and its digest, if present) and we shouldn't be using PDO to calculate its offset. This fixes handling for the C2HTermReq PDUs, as it used to be broken and usually (if target set PDO=0) resulted in an overflow when calculating psh_len. Signed-off-by: Konrad Sztyber <konrad.sztyber@intel.com> Change-Id: Ia2976517019469ba375eb32d22739372211eff35 Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/12846 Community-CI: Broadcom CI <spdk-ci.pdl@broadcom.com> Community-CI: Mellanox Build Bot Tested-by: SPDK CI Jenkins <sys_sgci@intel.com> Reviewed-by: Jim Harris <james.r.harris@intel.com> Reviewed-by: Aleksey Marchuk <alexeymar@nvidia.com>		2022-06-01 08:56:58 +00:00
..
linux	vhost: update virtion_config.h and virtio_ring.h	2019-12-20 10:04:27 +00:00
spdk	version: SPDK 22.09 pre	2022-05-23 19:53:29 +00:00
spdk_internal	nvme/tcp: check PDU type before checking padding	2022-06-01 08:56:58 +00:00
Makefile	build: Copy headers to build/include on build	2020-06-15 15:27:16 +00:00