diff options
| author | Mi Jinlong <mijinlong@cn.fujitsu.com> | 2011-03-10 17:43:37 +0800 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2011-03-16 11:10:22 -0400 |
| commit | d2b217439fd1d8f7857175f063113f4d1d66306c (patch) | |
| tree | 35d8c2463a53de77b20ae6d37807b04d33ecfedb /virt | |
| parent | 0a5e5f122c756d1c1a6ca712eda76ea8664e5fd9 (diff) | |
| download | linux-3.10-d2b217439fd1d8f7857175f063113f4d1d66306c.tar.gz linux-3.10-d2b217439fd1d8f7857175f063113f4d1d66306c.tar.bz2 linux-3.10-d2b217439fd1d8f7857175f063113f4d1d66306c.zip | |
nfs41: make sure nfs server return right ca_maxresponsesize_cached
According to rfc5661,
ca_maxresponsesize_cached:
Like ca_maxresponsesize, but the maximum size of a reply that
will be stored in the reply cache (Section 2.10.6.1). For each
channel, the server MAY decrease this value, but MUST NOT
increase it.
the latest kernel(2.6.38-rc8) may increase the value for ignoring
request's ca_maxresponsesize_cached value. We should not ignore it.
Signed-off-by: Mi Jinlong <mijinlong@cn.fujitsu.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions