[chrony-dev] [Git][chrony/chrony][master] 8 commits: hwclock: don't drop valid samples in HCL_ProcessReadings()

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-dev Archives ]


Title: GitLab

Miroslav Lichvar pushed to branch master at chrony / chrony

Commits:

  • 55353848
    by Miroslav Lichvar at 2025-08-14T14:24:54+02:00
    hwclock: don't drop valid samples in HCL_ProcessReadings()
    
    Modify the HCL_ProcessReadings() function to try to always provide
    a valid sample. Instead of dropping a sample outside of the expected
    delay, provide its assumed quality level as a small integer (relative to
    already accumulated samples), and let the caller decide what quality is
    acceptable.
    
  • 51d161a0
    by Miroslav Lichvar at 2025-08-14T14:25:38+02:00
    refclock: rework update of reachability again
    
    The recent rework of refclock reachability to better work with
    driver-specific filtering (PHC driver dropping samples with unexpected
    delay) introduced an issue that a PPS refclock is indicated as reachable
    even when its "lock" refclock is permanently unreachable, or its samples
    constistently fail in other sample checks, and no actual samples can be
    accumulated. This breaks the new maxunreach option.
    
    Rework the refclock code to provide samples from drivers together with
    their quality level (all drivers except PHC provide samples with
    constant quality of 1) and drop samples with quality 0 after passing
    all checks, right before the actual accumulation in the median sample
    filter. Increment the reachability counter only for samples that would
    be accumulated.
    
    This fixes the problem with refclocks indicated as reachable when their
    samples would be dropped for other reasons than the PHC-specific delay
    filter, and the maxunreach option can work as expected.
    
    Fixes: b9b338a8df23 ("refclock: rework update of reachability")
    
  • 6c597374
    by Miroslav Lichvar at 2025-08-14T14:25:38+02:00
    configure: fix compiler warnings in system function checks
    
    Avoid using (void *)1 as an output buffer to fix detection of supported
    system functions due to -Werror and -Wstringop-overflow etc.
    
  • d3f3638b
    by Miroslav Lichvar at 2025-08-14T15:30:27+02:00
    util: avoid compiler warning in UTI_IPSockAddrToString()
    
    Don't print directly a buffer of the pool to another buffer of
    the pool to avoid a -Wrestrict warning produced by a recent gcc version.
    
  • 4886c776
    by Miroslav Lichvar at 2025-08-14T15:30:27+02:00
    update copyright years
    
  • 487cf384
    by Miroslav Lichvar at 2025-08-14T15:30:27+02:00
    doc: update FAQ
    
  • 2cfe9699
    by Miroslav Lichvar at 2025-08-14T15:30:27+02:00
    doc: update credits in README
    
  • e9848c01
    by Miroslav Lichvar at 2025-08-14T15:55:15+02:00
    doc: update NEWS
    

21 changed files:



Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/