On Fri, 9 Feb 2018 13:31:12 -0500, J. Bruce Fields wrote: >> For NFSv4, you would have the option of returning NFS4ERR_RESOURCE or >> possibly NFS4ERR_INVAL (personally, I'd prefer the latter, since >> NFS4ERR_RESOURCE is too wooly). >> >> For NFSv4.1 or above, you probably have a choice of NFS4ERR_REQ_TOO_BIG >> (if the size is greater than ca_maxrequestsize) or NFS4ERR_INVAL. > > I think this sort of problem is typically found early in the rpc code > (probably the check against sv_max_mesg in > net/sunrpc/svcsock.c:svc_tcp_recv_record()). It drops the connection. > I'm not sure why. It looks implemented long time ago. [PATCH] PATCH 11/16: NFSD: TCP: close bad connections https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/commit/?id=84e9f22a623a Regards, Ikarashi -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
