Project

General

Profile

Actions
Copy link

Bug #1541

closed

flock: a single request can get multiple locks set

Added by Greg Farnum over 12 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
High
Assignee:
Greg Farnum
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I probably broke this when I removed the auto-setting of waiting locks. Now a single client request to lock can result in a lock going in, and then going in again after the unlock.

Actions
Copy link
 #1

Updated by Greg Farnum over 12 years ago

  • Status changed from New to In Progress

Actually, it's that the waiting_locks list isn't getting cleared, and then an unlock attempt clears that instead of the real lock. I've got a fix for that and am testing some related stuff before I push.

Actions
Copy link
 #2

Updated by Greg Farnum over 12 years ago

  • Status changed from In Progress to Resolved

Merged this and a couple other fixes to master in commit:9cd0b5d2269227bf96ef543984750b9a6addb929

Actions
Copy link
 #3

Updated by John Spray over 7 years ago

  • Project changed from Ceph to CephFS
  • Category deleted (1)
  • Target version deleted (v0.36)

Bulk updating project=ceph category=mds bugs so that I can remove the MDS category from the Ceph project to avoid confusion.

Actions
Copy link

Also available in: Atom PDF