diff options
author | Xiubo Li <xiubli@redhat.com> | 2023-06-13 07:49:59 +0300 |
---|---|---|
committer | Ilya Dryomov <idryomov@gmail.com> | 2023-06-30 13:08:55 +0300 |
commit | ce72d4e0f179340cece90d5b826eb63bbf9fefc0 (patch) | |
tree | 5d8942adc5006b0306239623dcb81773b8119300 /scripts/gdb/linux/vmalloc.py | |
parent | 2d12ad950b0c2a89d82f5d258309ad23aa70fc38 (diff) | |
download | linux-ce72d4e0f179340cece90d5b826eb63bbf9fefc0.tar.xz |
ceph: issue a cap release immediately if no cap exists
In case:
mds client
- Releases cap and put Inode
- Increase cap->seq and sends
revokes req to the client
- Receives release req and - Receives & drops the revoke req
skip removing the cap and
then eval the CInode and
issue or revoke caps again.
- Receives & drops the caps update
or revoke req
- Health warning for client
isn't responding to
mclientcaps(revoke)
All the IMPORT/REVOKE/GRANT cap ops will increase the session seq
in MDS side and then the client need to issue a cap release to
unblock MDS to remove the corresponding cap to unblock possible
waiters.
Link: https://tracker.ceph.com/issues/61332
Signed-off-by: Xiubo Li <xiubli@redhat.com>
Reviewed-by: Milind Changire <mchangir@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Diffstat (limited to 'scripts/gdb/linux/vmalloc.py')
0 files changed, 0 insertions, 0 deletions