Project

General

Profile

Actions

Bug #40872

closed

rgw: when usring radosgw-admin to list bucket, can set --max-entries excessively high

Added by J. Eric Ivancich almost 5 years ago. Updated over 4 years ago.

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

0%

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

Description

When listing a bucket with radosgw-admin, the user can specify the
maximum number of entries. That number can be unreasonably large, and
can affect the performance and memory availability. For example:

radosgw-admin bucket list --bucket mybucket1 --max-entries=10000000

This has the potential for creating large data structures at multiple
levels in the the call stack of the radosgw(-admin) process,
potentially causing the process to run out of memory. This change
limits the maximum number of entries requested in all but the high
level code to help mitigate this issue.


Related issues 4 (0 open4 closed)

Related to rgw - Bug #41655: rgw: fix minimum of unordered bucket listingResolvedJ. Eric Ivancich09/04/2019

Actions
Copied to rgw - Backport #41102: nautilus: rgw: when usring radosgw-admin to list bucket, can set --max-entries excessively highResolvedJ. Eric IvancichActions
Copied to rgw - Backport #41103: mimic: rgw: when usring radosgw-admin to list bucket, can set --max-entries excessively highResolvedNathan CutlerActions
Copied to rgw - Backport #41104: luminous: rgw: when usring radosgw-admin to list bucket, can set --max-entries excessively highResolvedNathan CutlerActions
Actions

Also available in: Atom PDF