Bug 1396930 - chronyd crashes when performing server leap smear
Summary: chronyd crashes when performing server leap smear
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: chrony
Version: 7.3
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: rc
: ---
Assignee: Miroslav Lichvar
QA Contact: Jakub Prokes
URL:
Whiteboard:
Depends On: 1392793
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-21 08:43 UTC by Marcel Kolaja
Modified: 2017-03-08 16:07 UTC (History)
9 users (show)

Fixed In Version: chrony-2.1.1-4.el7_3
Doc Type: Bug Fix
Doc Text:
When chronyd was configured with the smoothtime directive and the leaponly option to perform a server leap smear, the direction of smoothing could be determined incorrectly due to numerical errors in floating point operations. This consequently caused an assertion failure and chronyd terminated unexpectedly. A patch has been applied, which ensures that the direction is calculated and applied correctly when small offsets are employed in a time update.
Clone Of: 1392793
Environment:
Last Closed: 2016-12-06 17:12:47 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 2759021 0 None None None 2016-12-02 02:40:20 UTC
Red Hat Product Errata RHBA-2016:2887 0 normal SHIPPED_LIVE chrony bug fix update 2016-12-06 22:02:01 UTC

Description Marcel Kolaja 2016-11-21 08:43:33 UTC 
This bug has been copied from bug #1392793 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 6 errata-xmlrpc 2016-12-06 17:12:47 UTC 
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, 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://rhn.redhat.com/errata/RHBA-2016-2887.html
Note You need to log in before you can comment on or make changes to this bug.