Bug 1396420 - Integer overflow in cn=monitor counters
Summary: Integer overflow in cn=monitor counters
Keywords:
Status: CLOSED DUPLICATE of bug 1377452
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Noriko Hosoi
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-18 09:41 UTC by Viktor Ashirov
Modified: 2020-09-13 21:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-20 15:12:45 UTC
Target Upstream Version:


Attachments (Terms of Use)
bytessent_overflow_test.py (2.71 KB, text/plain)
2016-11-18 11:56 UTC, Viktor Ashirov
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 2104 0 None None None 2020-09-13 21:53:38 UTC

Description Viktor Ashirov 2016-11-18 09:41:55 UTC
Description of problem:
In cn=monitor bytessent and possibly other values (like entriessent, opsinitiated, opscompleted) are overflowing at 2^32-1.

Version-Release number of selected component (if applicable):
389-ds-base-1.3.5.10-11.el7

How reproducible:
always

Steps to Reproduce:
1. Add 100k entries
2. Search for all entries
3. Check value of bytessent in cn=monitor
4. Repeat steps 2-3 

Actual results:
After some time bytessent passes 2^32-1 boundary and starts from 0

Expected results:
Max value of bytessent is expected to be 2^64-1.

Additional info:
389-ds-base-1.2.11 is not affected.

Comment 1 Viktor Ashirov 2016-11-18 11:56:55 UTC
Created attachment 1221855 [details]
bytessent_overflow_test.py

Comment 2 Noriko Hosoi 2016-11-18 17:29:56 UTC
Upstream ticket:
https://fedorahosted.org/389/ticket/49045

Comment 3 mreynolds 2017-03-20 15:12:45 UTC
Going to close this as a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1377452

*** This bug has been marked as a duplicate of bug 1377452 ***


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