Bug #39021
closed
Several race conditions are possible between io::ObjectRequest and io::CopyupRequest
Added by Jason Dillaman about 5 years ago.
Updated over 3 years ago.
Backport:
luminous,mimic,nautilus
Description
The snap/parent locks are inconsistently held in numerous locations which could result in a race between IO execution and an image refresh. Additionally, nothing is currently preventing two copyup requests from executing concurrently once the parent image has been read (and it's removed from the in-flight copyup list).
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
- Status changed from In Progress to Pending Backport
- Pull request ID set to 27357
- Copied to Backport #39194: luminous: Several race conditions are possible between io::ObjectRequest and io::CopyupRequest added
- Copied to Backport #39195: nautilus: Several race conditions are possible between io::ObjectRequest and io::CopyupRequest added
- Copied to Backport #39196: mimic: Several race conditions are possible between io::ObjectRequest and io::CopyupRequest added
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Also available in: Atom
PDF