48b2e94f66
The Linux kernel NVMe-oF target can easily be misconfigured to report newline-terminated strings from the discovery service, since its parameters are set by echoing into sysfs files, and echo adds a newline by default. Newline characters are not allowed as part of the TRADDR and TRSVCID fields, since they are defined as ASCII strings in the NVMe specification sense, which limits the acceptable characters to the 0x20-0x7E range. However, we can add a workaround for misconfigured targets with trailing newlines that shouldn't impact any valid configurations. Change-Id: I5db183d5637128fa8d50c245f4bfa965cc3ce8e2 Signed-off-by: Daniel Verkamp <daniel.verkamp@intel.com> Reviewed-on: https://review.gerrithub.io/370593 Reviewed-by: Ben Walker <benjamin.walker@intel.com> Tested-by: SPDK Automated Test System <sys_sgsw@intel.com> |
||
---|---|---|
.. | ||
bdev | ||
blob | ||
blobfs | ||
conf | ||
copy | ||
cunit | ||
env_dpdk | ||
event | ||
ioat | ||
iscsi | ||
json | ||
jsonrpc | ||
log | ||
net | ||
nvme | ||
nvmf | ||
rocksdb | ||
rpc | ||
scsi | ||
trace | ||
ut_mock | ||
util | ||
vhost | ||
Makefile |