mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-09-13 14:14:37 +00:00
a0544c946d
RFC 5666 Section 4.2 states: > When the peer detects an RPC-over-RDMA header version that it does > not support (currently this document defines only version 1), it > replies with an error code of ERR_VERS, and provides the low and > high inclusive version numbers it does, in fact, support. And: > When other decoding errors are detected in the header or chunks, > either an RPC decode error MAY be returned or the RPC/RDMA error > code ERR_CHUNK MUST be returned. The Linux NFS server does throw ERR_VERS when a client sends it a request whose rdma_version is not "one." But it does not return ERR_CHUNK when a header decoding error occurs. It just drops the request. To improve protocol extensibility, it should reject invalid values in the rdma_proc field instead of treating them all like RDMA_MSG. Otherwise clients can't detect when the server doesn't support new rdma_proc values. Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Reviewed-by: Devesh Sharma <devesh.sharma@broadcom.com> Tested-by: Devesh Sharma <devesh.sharma@broadcom.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com> |
||
|---|---|---|
| .. | ||
| backchannel.c | ||
| fmr_ops.c | ||
| frwr_ops.c | ||
| Makefile | ||
| module.c | ||
| physical_ops.c | ||
| rpc_rdma.c | ||
| svc_rdma.c | ||
| svc_rdma_backchannel.c | ||
| svc_rdma_marshal.c | ||
| svc_rdma_recvfrom.c | ||
| svc_rdma_sendto.c | ||
| svc_rdma_transport.c | ||
| transport.c | ||
| verbs.c | ||
| xprt_rdma.h | ||