summaryrefslogtreecommitdiffstats
path: root/fs/afs/fsclient.c
diff options
context:
space:
mode:
authorDavid Howells <dhowells@redhat.com>2019-05-16 13:21:59 +0100
committerDavid Howells <dhowells@redhat.com>2019-05-16 16:25:20 +0100
commit94f699c9cdb11b8f53cb70624b69aeae16f26db2 (patch)
treef528d331b014f7914518024fb536108ab905cce2 /fs/afs/fsclient.c
parentbbd172e31696709b58eb492fafb574985b778326 (diff)
downloadlinux-stable-94f699c9cdb11b8f53cb70624b69aeae16f26db2.tar.gz
linux-stable-94f699c9cdb11b8f53cb70624b69aeae16f26db2.tar.bz2
linux-stable-94f699c9cdb11b8f53cb70624b69aeae16f26db2.zip
afs: Fix the maximum lifespan of VL and probe calls
If an older AFS server doesn't support an operation, it may accept the call and then sit on it forever, happily responding to pings that make kafs think that the call is still alive. Fix this by setting the maximum lifespan of Volume Location service calls in particular and probe calls in general so that they don't run on endlessly if they're not supported. Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'fs/afs/fsclient.c')
-rw-r--r--fs/afs/fsclient.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/afs/fsclient.c b/fs/afs/fsclient.c
index 1296f5dc4c1e..7051b58d8a55 100644
--- a/fs/afs/fsclient.c
+++ b/fs/afs/fsclient.c
@@ -2115,6 +2115,7 @@ struct afs_call *afs_fs_get_capabilities(struct afs_net *net,
call->upgrade = true;
call->want_reply_time = true;
call->async = true;
+ call->max_lifespan = AFS_PROBE_MAX_LIFESPAN;
/* marshall the parameters */
bp = call->request;