Actions
Bug #40872
closedrgw: when usring radosgw-admin to list bucket, can set --max-entries excessively high
% Done:
0%
Source:
Tags:
Backport:
nautilus, mimic, luminous
Regression:
No
Severity:
3 - minor
Reviewed:
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.
Updated by J. Eric Ivancich almost 5 years ago
- Status changed from 7 to Pending Backport
Updated by Patrick Donnelly almost 5 years ago
- Copied to Backport #41102: nautilus: rgw: when usring radosgw-admin to list bucket, can set --max-entries excessively high added
Updated by Patrick Donnelly almost 5 years ago
- Copied to Backport #41103: mimic: rgw: when usring radosgw-admin to list bucket, can set --max-entries excessively high added
Updated by Patrick Donnelly almost 5 years ago
- Copied to Backport #41104: luminous: rgw: when usring radosgw-admin to list bucket, can set --max-entries excessively high added
Updated by Nathan Cutler over 4 years ago
- Related to Bug #41655: rgw: fix minimum of unordered bucket listing added
Updated by Nathan Cutler over 4 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