+1
−3
Loading
Previously, if a non-fabrics transport wanted to execute fabrics
commands (e.g. to emulate register access by a PROPERTY_{GET,SET}
command), it had to use spdk_nvmf_request_exec_fabrics(). However,
because we want to remove this function in the future,
spdk_nvmf_request_exec() needs to allow non-fabrics transports to
execute fabrics commands. This also means that such transports are now
responsible for rejecting fabrics commands sent by hosts.
Signed-off-by:
Konrad Sztyber <konrad.sztyber@intel.com>
Change-Id: I23d7e89b6045dcfeeeff398469e80d408059efdb
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/22237
Reviewed-by:
Changpeng Liu <changpeng.liu@intel.com>
Reviewed-by:
Jim Harris <jim.harris@samsung.com>
Reviewed-by:
Jacek Kalwas <jacek.kalwas@intel.com>
Community-CI: Mellanox Build Bot
Tested-by:
SPDK CI Jenkins <sys_sgci@intel.com>
Reviewed-by:
Aleksey Marchuk <alexeymar@nvidia.com>