Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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 (iputils bug fix and enhancement 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/RHBA-2021:1683
Description of problem: incorrect "time" in ping statistics Version-Release number of selected component (if applicable): iputils-20180629-2.el8 How reproducible: Steps to Reproduce: 1.ping any host 2.check the output 3."time" in ping statistics is incorrect Actual results: RHEL 8 : # ping vm67 PING vm67 (192.168.122.142) 56(84) bytes of data. 64 bytes from vm67 (192.168.122.142): icmp_seq=1 ttl=64 time=0.692 ms 64 bytes from vm67 (192.168.122.142): icmp_seq=2 ttl=64 time=1.02 ms 64 bytes from vm67 (192.168.122.142): icmp_seq=3 ttl=64 time=1.06 ms 64 bytes from vm67 (192.168.122.142): icmp_seq=4 ttl=64 time=0.928 ms 64 bytes from vm67 (192.168.122.142): icmp_seq=5 ttl=64 time=0.520 ms ^C --- vm67 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, ***time 10ms*** rtt min/avg/max/mdev = 0.520/0.842/1.058/0.207 ms Expected results: RHEL 7: # ping vm67 PING vm67 (192.168.122.142) 56(84) bytes of data. 64 bytes from vm67 (192.168.122.142): icmp_seq=1 ttl=64 time=0.562 ms 64 bytes from vm67 (192.168.122.142): icmp_seq=2 ttl=64 time=0.677 ms 64 bytes from vm67 (192.168.122.142): icmp_seq=3 ttl=64 time=0.680 ms 64 bytes from vm67 (192.168.122.142): icmp_seq=4 ttl=64 time=0.383 ms ^C --- vm67 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, ****time 3003ms**** rtt min/avg/max/mdev = 0.383/0.575/0.680/0.123 ms Additional info: ~~source code~~ /RHEL-8/iputils/20180629/2.el8/iputils-s20180629/ping_common.c 937 printf(", time %ldms", (1000*tv.tv_sec+tv.tv_usec+500)/1000); ~~~~~~~~~~~~~~~ tv_sec is second tv_usec is Microsecond 1000000 Microsecond = 1 second So 1000*tv.tv_sec can't add tv.tv_usec directly.