rbd: exclusive mapping (-o exclusive) fixes
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | rbd: rename RBD_LOCK_STATE_RELEASING and releasing_waitdrivers/ | +10 | 1 reply | |
| 2/3 | rbd: don't assume RBD_LOCK_STATE_LOCKED for exclusive mappingsdrivers/ | +5 | 0 replies | |
| 3/3 | rbd: don't assume rbd_is_lock_owner() for exclusive mappingsdrivers/ | +0 | 4 replies |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Dongsheng Yang |
|---|---|
| 1/3 | R-b |
| 2/3 | |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] rbd: exclusive mapping (-o exclusive) fixes
Hello,
This addresses incorrect assumptions on rbd_dev->lock_state in rbd_img_exclusive_lock() and rbd_add_acquire_lock() which could lead to issues with exclusive mappings in the face of watch errors.
Thanks,
Ilya
Ilya Dryomov (3):
rbd: rename RBD_LOCK_STATE_RELEASING and releasing_wait
rbd: don't assume RBD_LOCK_STATE_LOCKED for exclusive mappings
rbd: don't assume rbd_is_lock_owner() for exclusive mappings
drivers/block/rbd.c | 35 +++++++++++++++-------------------- 1 file changed, 15 insertions(+), 20 deletions(-)
Signature · 1 line
2.45.1