Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kraken: cephfs: Deadlock on two ceph-fuse clients accessing the same file #16191

Merged
merged 1 commit into from Jul 19, 2017

Conversation

smithfarm
Copy link
Contributor

After Locker::issue_new_caps() adds new Capability data struct,
do not issue caps immediately. Let CInode::encode_inodestate()
do the job instead. This can avoid various races that early reply
is not allowed, caps that haven't been sent to client gets revoked.

Fixes: http://tracker.ceph.com/issues/19635
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
(cherry picked from commit 799703a)
@smithfarm smithfarm self-assigned this Jul 6, 2017
@smithfarm smithfarm added this to the kraken milestone Jul 6, 2017
@smithfarm smithfarm changed the title kraken: Deadlock on two ceph-fuse clients accessing the same file kraken: cephfs: Deadlock on two ceph-fuse clients accessing the same file Jul 6, 2017
@smithfarm smithfarm added cephfs Ceph File System and removed core labels Jul 6, 2017
@smithfarm
Copy link
Contributor Author

@ukernel @batrick This PR passed an fs suite at http://tracker.ceph.com/issues/19009#note-67

Please review.

@smithfarm smithfarm merged commit e26575b into ceph:kraken Jul 19, 2017
@smithfarm smithfarm deleted the wip-20028-kraken branch July 19, 2017 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-fix cephfs Ceph File System
Projects
None yet
2 participants