afs: Fix use of afs_check_for_remote_deletion()
authorDavid Howells <dhowells@redhat.com>
Mon, 15 Jun 2020 23:34:09 +0000 (00:34 +0100)
committerDavid Howells <dhowells@redhat.com>
Tue, 16 Jun 2020 15:26:57 +0000 (16:26 +0100)
commit728279a5a1fd9fa9fa268f807391c4d19ad2822c
tree14449edf632b36d26b200931233b844fdaab9683
parent44767c353127cfcbee49a89bab39a3680ecd2a45
afs: Fix use of afs_check_for_remote_deletion()

afs_check_for_remote_deletion() checks to see if error ENOENT is returned
by the server in response to an operation and, if so, marks the primary
vnode as having been deleted as the FID is no longer valid.

However, it's being called from the operation success functions, where no
abort has happened - and if an inline abort is recorded, it's handled by
afs_vnode_commit_status().

Fix this by actually calling the operation aborted method if provided and
having that point to afs_check_for_remote_deletion().

Fixes: e49c7b2f6de7 ("afs: Build an abstraction around an "operation" concept")
Signed-off-by: David Howells <dhowells@redhat.com>
fs/afs/dir.c
fs/afs/dir_silly.c
fs/afs/file.c
fs/afs/flock.c
fs/afs/fs_operation.c
fs/afs/inode.c
fs/afs/internal.h