afs: Fix to actually set AFS_SERVER_FL_HAVE_EPOCH
commit69cf3978f3
upstream. 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:3bf0fb6f33
("afs: Probe multiple fileservers simultaneously") Signed-off-by: David Howells <dhowells@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
c2bdc86ec8
commit
f581eff939
|
@ -169,7 +169,7 @@ static int afs_record_cm_probe(struct afs_call *call, struct afs_server *server)
|
|||
|
||||
spin_lock(&server->probe_lock);
|
||||
|
||||
if (!test_bit(AFS_SERVER_FL_HAVE_EPOCH, &server->flags)) {
|
||||
if (!test_and_set_bit(AFS_SERVER_FL_HAVE_EPOCH, &server->flags)) {
|
||||
server->cm_epoch = call->epoch;
|
||||
server->probe.cm_epoch = call->epoch;
|
||||
goto out;
|
||||
|
|
Loading…
Reference in New Issue