rbd: keep reference to lingering object requests
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 7 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | rbd: unregister linger in watch sync routinedrivers/ | +0 | 1 reply | |
| 2/4 | rbd: track object rather than osd request for watchdrivers/ | +1 | 1 reply | |
| 3/4 | rbd: decrement obj request count when deletingdrivers/ | +0 | 1 reply | |
| 4/4 | rbd: don't drop watch requests on completiondrivers/ | +0 | 4 replies |
Reviews trailers per patch
3 of 4 patches have a Reviewed-by or Acked-by.
| Patch | Josh Durgin |
|---|---|
| 1/4 | R-b |
| 2/4 | R-b |
| 3/4 | R-b |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] rbd: keep reference to lingering object requests
This series applies on top of the new rbd request code.
When an osd request is marked to linger the osd client will keep a copy of the request, and will resubmit it if necessary. If it gets resubmitted, it will also call the completion routine again, and because of that we need to make sure the associated object request structure remains valid. The last patch in this series ensures that by taking an extra reference for an object request set to linger.
-Alex
[PATCH 1/4] rbd: unregister linger in watch sync routine [PATCH 2/4] rbd: track object rather than osd request for watch [PATCH 3/4] rbd: decrement obj request count when deleting [PATCH 4/4] rbd: don't drop watch requests on completion