Project

General

Profile

Actions
Copy link

Bug #17618

closed

Exclusive lock improperly initialized on read-only image when using snap_set API

Added by Jason Dillaman over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

When using the librbd API to switch between a snapshot and then back to the HEAD revision, the exclusive lock will be (partially) initialized if the image is in read-only mode. The exclusive lock should not be initialized when in read-only mode.

Related issues 1 (0 open — 1 closed)

Copied to rbd - Backport #17766: jewel: Exclusive lock improperly initialized on read-only image when using snap_set APIResolvedLoïc DacharyActions
Actions
Copy link
 #1

Updated by Jason Dillaman over 7 years ago

  • Status changed from In Progress to Fix Under Review
Actions
Copy link
 #2

Updated by Mykola Golub over 7 years ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #3

Updated by Loïc Dachary over 7 years ago

  • Copied to Backport #17766: jewel: Exclusive lock improperly initialized on read-only image when using snap_set API added
Actions
Copy link
 #4

Updated by Nathan Cutler about 7 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF