b95fc6fc64
This one is actually a bit tough to deduce in the specification. The NVMe-oF spec says that QID errors detected in the RDMA transport shall return an RDMA-specific error indicating the problem. However, our code doesn't detect the error in RDMA-specific code, and it isn't clear if the language is a "must" or a "should". The NVMe specification does clearly indicate what error to return on invalid QID in response to a Create I/O Queue Pair command. For now, return that while we game plan whether we need to call into the RDMA transport to correctly report this error. Change-Id: I7faf37bad9b9202bc50a906214a51c17e4808fc0 Signed-off-by: Ben Walker <benjamin.walker@intel.com> Reviewed-on: https://review.gerrithub.io/413858 Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> Reviewed-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> |
||
|---|---|---|
| .. | ||
| ctrlr_bdev.c | ||
| ctrlr_discovery.c | ||
| ctrlr.c | ||
| Makefile | ||
| nvmf_internal.h | ||
| nvmf.c | ||
| rdma.c | ||
| request.c | ||
| subsystem.c | ||
| transport.c | ||
| transport.h | ||