Project

General

Profile

Actions
Copy link

Bug #19066

closed

rgw_file: ensure valid_s3_object_name for directories

Added by Matt Benjamin about 7 years ago. Updated over 6 years ago.

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

0%

Source:
Tags:
Backport:
jewel kraken
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

The logic in RGWLibFS::mkdir() validated bucket names, but not
object names (though RGWLibFS::create() did so).

The negative side effect of this was not creating illegal objects
(we won't), but in a) failing with -EIO and b) more importantly,
not removing up the proposed object from FHCache, which produced a
boost assert when recycled.

Related issues 2 (0 open — 2 closed)

Copied to rgw - Backport #19115: jewel: rgw_file: ensure valid_s3_object_name for directoriesResolvedAlexey SheplyakovActions
Copied to rgw - Backport #19149: kraken: rgw_file: ensure valid_s3_object_name for directoriesResolvedNathan CutlerActions
Actions
Copy link
 #1

Updated by Matt Benjamin about 7 years ago

  • Status changed from In Progress to Pending Backport
Actions
Copy link
 #2

Updated by Alexey Sheplyakov about 7 years ago

  • Copied to Backport #19115: jewel: rgw_file: ensure valid_s3_object_name for directories added
Actions
Copy link
 #3

Updated by Nathan Cutler about 7 years ago

  • Copied to Backport #19149: kraken: rgw_file: ensure valid_s3_object_name for directories added
Actions
Copy link
 #4

Updated by Nathan Cutler over 6 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF