OSDN Git Service

afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH
authorDavid Howells <dhowells@redhat.com>
Fri, 24 Apr 2020 10:21:14 +0000 (11:21 +0100)
committerDavid Howells <dhowells@redhat.com>
Fri, 24 Apr 2020 15:32:49 +0000 (16:32 +0100)
commit69cf3978f3ada4e54beae4ad44868b5627864884
treed616b4cd3a121ee9f0f54f1384a314c3932ea938
parentbe59167c8f27592e79c0044a0bbc515b38d5eace
afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH

AFS keeps track of the epoch value from the rxrpc protocol to note (a) when
a fileserver appears to have restarted and (b) when different endpoints of
a fileserver do not appear to be associated with the same fileserver
(ie. all probes back from a fileserver from all of its interfaces should
carry the same epoch).

However, the AFS_SERVER_FL_HAVE_EPOCH flag that indicates that we've
received the server's epoch is never set, though it is used.

Fix this to set the flag when we first receive an epoch value from a probe
sent to the filesystem client from the fileserver.

Fixes: 3bf0fb6f33dd ("afs: Probe multiple fileservers simultaneously")
Signed-off-by: David Howells <dhowells@redhat.com>
fs/afs/cmservice.c