diff options
| author | Xiubo Li <xiubli@redhat.com> | 2023-06-28 01:57:09 +0200 |
|---|---|---|
| committer | Ilya Dryomov <idryomov@gmail.com> | 2023-06-30 12:08:55 +0200 |
| commit | 257e6172ab36ebbe295a6c9ee9a9dd0fe54c1dc2 (patch) | |
| tree | f063bf2f61d99cb7a42777e60fa5468eb41d111b /scripts/spdxexclude | |
| parent | ceph: issue a cap release immediately if no cap exists (diff) | |
| download | linux-257e6172ab36ebbe295a6c9ee9a9dd0fe54c1dc2.tar.xz linux-257e6172ab36ebbe295a6c9ee9a9dd0fe54c1dc2.zip | |
ceph: don't let check_caps skip sending responses for revoke msgs
If a client sends out a cap update dropping caps with the prior 'seq'
just before an incoming cap revoke request, then the client may drop
the revoke because it believes it's already released the requested
capabilities.
This causes the MDS to wait indefinitely for the client to respond
to the revoke. It's therefore always a good idea to ack the cap
revoke request with the bumped up 'seq'.
Cc: stable@vger.kernel.org
Link: https://tracker.ceph.com/issues/61782
Signed-off-by: Xiubo Li <xiubli@redhat.com>
Reviewed-by: Milind Changire <mchangir@redhat.com>
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
Diffstat (limited to 'scripts/spdxexclude')
0 files changed, 0 insertions, 0 deletions