diff options
| author | NeilBrown <neilb@suse.de> | 2012-10-31 12:16:01 +1100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-11-17 13:14:21 -0800 |
| commit | 095a51831f6e6956b80bd5f921f412a6530f1bc2 (patch) | |
| tree | d4af3eb384d6e4964ffdea238394ea99ae01627c /crypto | |
| parent | 110d3a25cc089af6a8b7ddee3f01e65aeb55ae49 (diff) | |
| download | kernel_samsung_smdk4412-095a51831f6e6956b80bd5f921f412a6530f1bc2.zip kernel_samsung_smdk4412-095a51831f6e6956b80bd5f921f412a6530f1bc2.tar.gz kernel_samsung_smdk4412-095a51831f6e6956b80bd5f921f412a6530f1bc2.tar.bz2 | |
NFS: fix bug in legacy DNS resolver.
commit 8d96b10639fb402357b75b055b1e82a65ff95050 upstream.
The DNS resolver's use of the sunrpc cache involves a 'ttl' number
(relative) rather that a timeout (absolute). This confused me when
I wrote
commit c5b29f885afe890f953f7f23424045cdad31d3e4
"sunrpc: use seconds since boot in expiry cache"
and I managed to break it. The effect is that any TTL is interpreted
as 0, and nothing useful gets into the cache.
This patch removes the use of get_expiry() - which really expects an
expiry time - and uses get_uint() instead, treating the int correctly
as a ttl.
This fixes a regression that has been present since 2.6.37, causing
certain NFS accesses in certain environments to incorrectly fail.
Reported-by: Chuck Lever <chuck.lever@oracle.com>
Tested-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions