Bug 2390980 - RGW crash observed during copy-object ops with copy-source being empty
Summary: RGW crash observed during copy-object ops with copy-source being empty
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 8.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 8.1z4
Assignee: Casey Bodley
QA Contact: Chaithra
Rivka Pollack
URL:
Whiteboard:
Depends On:
Blocks: 2412218 2412237
TreeView+ depends on / blocked
 
Reported: 2025-08-26 04:39 UTC by Chaithra
Modified: 2025-11-12 02:39 UTC (History)
5 users (show)

Fixed In Version: ceph-19.2.1-277
Doc Type: Bug Fix
Doc Text:
.Empty string in the `HTTP_X_AMZ_COPY_SOURCE` header no longer causes crashing Previously, the `HTTP_X_AMZ_COPY_SOURCE` header could have an empty string output, rather than NULL. When the empty string was passed to `RGWCopyObj::parse_copy_location()` the empty name would cause a crash. With this fix, a check is in place that the header contains a valid string.
Clone Of:
: 2412218 (view as bug list)
Environment:
Last Closed: 2025-11-12 02:39:09 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 72669 0 None None None 2025-09-04 15:12:54 UTC
Github ceph ceph pull 65159 0 None open rgw: Check if `HTTP_X_AMZ_COPY_SOURCE` header is empty 2025-09-04 15:13:13 UTC
Red Hat Issue Tracker RHCEPH-11999 0 None None None 2025-08-26 04:41:13 UTC
Red Hat Product Errata RHSA-2025:21068 0 None None None 2025-11-12 02:39:19 UTC

Comment 7 errata-xmlrpc 2025-11-12 02:39:09 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Red Hat Ceph Storage 8.1 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2025:21068


Note You need to log in before you can comment on or make changes to this bug.