+++ This bug was initially created as a clone of Bug #2159301 +++ Description of problem: _calculate_ops relying on a config which can be modified on the fly will cause a bug. e.g. A file has 20 objects and filer_max_purge_ops config was 10. calling PurgeQueue::_execute_item and _calculate_ops returns 10, so ops_in_flight add 10. adjust filer_max_purge_ops to 20 on the fly calling PurgeQueue::_execute_item_complete and _calculate_ops returns 20, so ops_in_flight dec 20. since ops_in_flight is uint64, this cause an overflow which makes ops_in_flight far more greater than max_purge_ops and can't go back to a reasonable value. filer_max_purge_ops will still work when _do_purge_range, so it's ok to ignore it here. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from RHEL Program Management on 2023-01-09 11:16:54 UTC --- Please specify the severity of this bug. Severity is defined here: https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.
Please specify the severity of this bug. Severity is defined here: https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity.
https://github.com/ceph/ceph/pull/49655 is in v17.2.6
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 (Moderate: Red Hat Ceph Storage 6.1 security and 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-2023:3623