diff options
| author | David Howells <dhowells@redhat.com> | 2020-06-16 00:34:09 +0100 |
|---|---|---|
| committer | David Howells <dhowells@redhat.com> | 2020-06-16 16:26:57 +0100 |
| commit | 728279a5a1fd9fa9fa268f807391c4d19ad2822c (patch) | |
| tree | 14449edf632b36d26b200931233b844fdaab9683 /fs/afs/flock.c | |
| parent | 44767c353127cfcbee49a89bab39a3680ecd2a45 (diff) | |
| download | linux-728279a5a1fd9fa9fa268f807391c4d19ad2822c.tar.bz2 | |
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>
Diffstat (limited to 'fs/afs/flock.c')
| -rw-r--r-- | fs/afs/flock.c | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/fs/afs/flock.c b/fs/afs/flock.c index 71eea2a908c7..ffb8575345ca 100644 --- a/fs/afs/flock.c +++ b/fs/afs/flock.c @@ -175,10 +175,7 @@ static void afs_kill_lockers_enoent(struct afs_vnode *vnode) static void afs_lock_success(struct afs_operation *op) { - struct afs_vnode *vnode = op->file[0].vnode; - _enter("op=%08x", op->debug_id); - afs_check_for_remote_deletion(op, vnode); afs_vnode_commit_status(op, &op->file[0]); } @@ -186,6 +183,7 @@ static const struct afs_operation_ops afs_set_lock_operation = { .issue_afs_rpc = afs_fs_set_lock, .issue_yfs_rpc = yfs_fs_set_lock, .success = afs_lock_success, + .aborted = afs_check_for_remote_deletion, }; /* |