diff options
| author | NeilBrown <[email protected]> | 2012-10-31 12:16:01 +1100 |
|---|---|---|
| committer | Trond Myklebust <[email protected]> | 2012-10-31 16:25:59 -0400 |
| commit | 8d96b10639fb402357b75b055b1e82a65ff95050 (patch) | |
| tree | 13e1e4d63538e1f0177b64fee0b8ab7e96786089 /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 2b1bc308f492589f7d49012ed24561534ea2be8c (diff) | |
NFS: fix bug in legacy DNS resolver.
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 <[email protected]>
Tested-by: Chuck Lever <[email protected]>
Cc: [email protected]
Signed-off-by: NeilBrown <[email protected]>
Signed-off-by: Trond Myklebust <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions