Actions
Bug #5222
closedkrbd: use per-rbd_dev mutex to protect header updates
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Currently updating header information for an rbd device
is protected by the control lock, which precludes
concurrent header updates to distinct devices.
There's no need to serialize this. There would be
no conflict in having all mapped images get header
updates simultaneously.
The mutex is used to protect from concurrent updates
on a single image header, and as such a mutex within
the rbd_dev structure could be used for protection.
Actions