jewel: common: Request exclusive lock if owner sends -ENOTSUPP for proxied maintenance op #10784

Merged
merged 1 commit into from Oct 18, 2016

Projects

None yet

3 participants

@dillaman @ldachary dillaman librbd: request exclusive lock if current owner cannot execute op
The initial krbd implementation will not support executing maintenance
ops and instead will return -EOPNOTSUPP. In this case, librbd can take
the lock and execute the operation.

Fixes: http://tracker.ceph.com/issues/16171
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit d2d2d90)
e6ac214
@dachary dachary self-assigned this Aug 19, 2016
@dachary dachary added this to the jewel milestone Aug 19, 2016
@dachary dachary added bug fix rbd feature and removed bug fix labels Aug 19, 2016
@dachary
Member
dachary commented Oct 17, 2016

@idryomov does this backport look good to merge ? It passed the rbd suite http://tracker.ceph.com/issues/17487#note-10 (except for two failures that are unrelated http://tracker.ceph.com/issues/17590 and http://tracker.ceph.com/issues/17262)

@idryomov
Contributor

Looks good. (As noted in the original PR, rbd suite doesn't exercise it - I ran a quick krbd test.)

@dachary
Member
dachary commented Oct 18, 2016

@idryomov sorry for missing that and thanks for testing. Next time feel free to just remind me I missed the relevant test and I'll do it.

@dachary dachary merged commit 82edc5b into ceph:jewel Oct 18, 2016

2 checks passed

Signed-off-by all commits in this PR are signed
Details
default Build finished.
Details
@theanalyst theanalyst changed the title from jewel: Request exclusive lock if owner sends -ENOTSUPP for proxied maintenance op to "jewel: common: Request exclusive lock if owner sends -ENOTSUPP for proxied maintenance op" Nov 17, 2016
@theanalyst theanalyst changed the title from "jewel: common: Request exclusive lock if owner sends -ENOTSUPP for proxied maintenance op" to jewel: common: Request exclusive lock if owner sends -ENOTSUPP for proxied maintenance op Nov 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment