From: Chuck Lever Date: Sun, 9 Nov 2014 01:15:18 +0000 (-0500) Subject: NFS: SETCLIENTID XDR buffer sizes are incorrect X-Git-Tag: omap-for-v3.19/fixes-rc1~150^2~3^2~1 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=6dd3436b9dc0df4b9ae7bb4e0076996a5ffda219;p=pandora-kernel.git NFS: SETCLIENTID XDR buffer sizes are incorrect Use the correct calculation of the maximum size of a clientaddr4 when encoding and decoding SETCLIENTID operations. clientaddr4 is defined in section 2.2.10 of RFC3530bis-31. The usage in encode_setclientid_maxsz is missing the 4-byte length in both strings, but is otherwise correct. decode_setclientid_maxsz simply asks for a page of receive buffer space, which is unnecessarily large (more than 4KB). Note that a SETCLIENTID reply is either clientid+verifier, or clientaddr4, depending on the returned NFS status. It doesn't hurt to allocate enough space for both. Signed-off-by: Chuck Lever Signed-off-by: Anna Schumaker --- Reading git-diff-tree failed