Is idenditfy ctrl cmd supposed to return a 'result' for RDMA?

[Daniel Wagner]

A bug was reported against nvme-cli that a setup works fine with
nvme-tcp but not with nvme-rdma[1]. The only difference I could spot
from user space PoV, is that RDMA returns 'funky' result values

# nvme id-ctrl /dev/nvme2 -vvv
opcode       : 06
flags        : 00
rsvd1        : 0000
nsid         : 00000000
cdw2         : 00000000
cdw3         : 00000000
data_len     : 00001000
metadata_len : 00000000
addr         : 3762f000
metadata     : 0
cdw10        : 00000001
cdw11        : 00000000
cdw12        : 00000000
cdw13        : 00000000
cdw14        : 00000000
cdw15        : 00000000
timeout_ms   : 00000000
result       : 3f3b0000
err          : 0
latency      : 7076 us

while for the same command, TCP returns 0.

I've tried to figure out where the source these values are

[ 4040.869872] nvmet: nvmet_execute_identify_ctrl:358
[ 4040.874002] nvme_submit_user_cmd:196 ffff88813f3b0000
[ 4040.875759] nvme_user_cmd:326 status 0 result ffff88813f3b0000

but got a bit lost in the RDMA code. So I am not sure, is this supposed to
happen?

[1] https://github.com/linux-nvme/libnvme/issues/807