Actions
Bug #58287
openrgwlc/notifications: initialize object state before accessing object size for use in notify
% Done:
0%
Source:
Tags:
lifecycle notification backport_processed
Backport:
pacific quincy reef
Regression:
No
Severity:
3 - minor
Reviewed:
Description
In remove_expired_obj(...), the value of obj->get_obj_size() is sent as the value for object size by the corresponding notification, but that is guaranteed to be 0 if obj->get_obj_state(...) has not been previously called (it hasn't).
This results in lc notifies sending 0 uniformly for obj_size, rather than the stored size.
Updated by Matt Benjamin over 1 year ago
- Status changed from In Progress to Fix Under Review
- Backport set to quincy
Updated by Casey Bodley over 1 year ago
- Has duplicate Bug #58282: zero size is reported for lifecycle notifications on versioned buckets added
Updated by Casey Bodley about 1 year ago
- Status changed from Fix Under Review to Pending Backport
- Tags set to lifecycle notification
- Backport changed from quincy to quincy reef
Updated by Backport Bot about 1 year ago
- Copied to Backport #59012: quincy: rgwlc/notifications: initialize object state before accessing object size for use in notify added
Updated by Backport Bot about 1 year ago
- Copied to Backport #59013: reef: rgwlc/notifications: initialize object state before accessing object size for use in notify added
Updated by Backport Bot about 1 year ago
- Tags changed from lifecycle notification to lifecycle notification backport_processed
Updated by Casey Bodley 11 months ago
- Tags changed from lifecycle notification backport_processed to lifecycle notification
- Backport changed from quincy reef to pacific quincy reef
Updated by Backport Bot 11 months ago
- Copied to Backport #61370: pacific: rgwlc/notifications: initialize object state before accessing object size for use in notify added
Updated by Backport Bot 11 months ago
- Tags changed from lifecycle notification to lifecycle notification backport_processed
Actions