Project

General

Profile

Bug #48874

multipart object names may have null characters

Added by Casey Bodley 5 months ago. Updated 3 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
multipart
Backport:
pacific, nautilus, octopus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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


Related issues

Related to rgw - Feature #49184: rgw: allow rgw-orphan-list to handle intermediate files w/ binary data Resolved
Copied to rgw - Backport #49129: pacific: multipart object names may have null characters Resolved
Copied to rgw - Backport #49130: nautilus: multipart object names may have null characters Resolved
Copied to rgw - Backport #49131: octopus: multipart object names may have null characters Resolved

History

#1 Updated by Casey Bodley 5 months ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 38905

#2 Updated by Casey Bodley 4 months ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport changed from nautilus, octopus to pacific, nautilus, octopus

#3 Updated by Backport Bot 4 months ago

  • Copied to Backport #49129: pacific: multipart object names may have null characters added

#4 Updated by Backport Bot 4 months ago

  • Copied to Backport #49130: nautilus: multipart object names may have null characters added

#5 Updated by Backport Bot 4 months ago

  • Copied to Backport #49131: octopus: multipart object names may have null characters added

#6 Updated by J. Eric Ivancich 4 months ago

  • Related to Feature #49184: rgw: allow rgw-orphan-list to handle intermediate files w/ binary data added

#7 Updated by Nathan Cutler 3 months 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".

Also available in: Atom PDF