diff options
author | Mi Jinlong <mijinlong@cn.fujitsu.com> | 2011-07-14 14:50:17 +0800 |
---|---|---|
committer | J. Bruce Fields <bfields@redhat.com> | 2011-07-15 18:58:51 -0400 |
commit | 1b74c25bc1a142ee8dd7ad080e2a974f28d1cb18 (patch) | |
tree | 99da76bc4a03e876e9f84e3a85a83518c4aa9bf9 /fs/freevxfs | |
parent | f197c27196a5e7631b89e2e92daa096fcf7c302c (diff) | |
download | linux-stable-1b74c25bc1a142ee8dd7ad080e2a974f28d1cb18.tar.gz linux-stable-1b74c25bc1a142ee8dd7ad080e2a974f28d1cb18.tar.bz2 linux-stable-1b74c25bc1a142ee8dd7ad080e2a974f28d1cb18.zip |
nfsd41: error out when client sets maxreq_sz or maxresp_sz too small
According to RFC5661, 18.36.3,
"if the client selects a value for ca_maxresponsesize such that
a replier on a channel could never send a response,the server
SHOULD return NFS4ERR_TOOSMALL in the CREATE_SESSION reply."
So, error out when the client sets a maxreq_sz less than the minimum
possible SEQUENCE request size, or sets a maxresp_sz less than the
minimum possible SEQUENCE reply size.
Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/freevxfs')
0 files changed, 0 insertions, 0 deletions