Actions
Bug #48874
closedmultipart object names may have null characters
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
multipart
Backport:
pacific, nautilus, octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
when a multipart upload races to write the part's head object, it generates a randomized prefix and tries again. this calls gen_rand_alphanumeric(), but didn't account for the trailing null character
Updated by Casey Bodley over 3 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 38905
Updated by Casey Bodley over 3 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport changed from nautilus, octopus to pacific, nautilus, octopus
Updated by Backport Bot over 3 years ago
- Copied to Backport #49129: pacific: multipart object names may have null characters added
Updated by Backport Bot over 3 years ago
- Copied to Backport #49130: nautilus: multipart object names may have null characters added
Updated by Backport Bot over 3 years ago
- Copied to Backport #49131: octopus: multipart object names may have null characters added
Updated by J. Eric Ivancich about 3 years ago
- Related to Feature #49184: rgw: allow rgw-orphan-list to handle intermediate files w/ binary data added
Updated by Nathan Cutler about 3 years ago
- 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".
Actions