From: vincent.debian@free.fr   
   Copy: jlu@pengutronix.de (Jan Luebbe)   
      
   --nxmHZJvvUC+EC8GY   
   Content-Type: text/plain; charset=utf-8   
   Content-Disposition: inline   
   Content-Transfer-Encoding: quoted-printable   
      
   [With the .deb file attached this time]   
      
   Le 2026-02-16 18:00, Vincent Blut a écrit :   
   > Control: tags -1 + moreinfo   
   >    
   > Le 2026-02-12 16:31, Vincent Blut a écrit :   
   > > Hi Salvatore,   
   > >    
   > > Le 2026-02-12 16:14, Salvatore Bonaccorso a écrit :   
   > > > Control: affects -1 - chrony   
   > > > Control: reassign -1 src:chrony 4.6.1-3   
   > > > Control: found -1 4.3-2+deb12u1   
   > > > Control: found -1 4.3-2   
   > > > Control: fixed -1 4.8-1   
   > > > Control: tags -1 + upstream fixed-upstream bookworm trixie   
   > > >    
   > > > Hi Jan,   
   > > >    
   > > > On Wed, Feb 11, 2026 at 11:40:12AM +0100, Jan Luebbe wrote:   
   > > > > Package: src:linux   
   > > > > Version: 6.12.69-1   
   > > > > Severity: important   
   > > > > Tags: upstream   
   > > > > X-Debbugs-Cc: jlu@pengutronix.de   
   > > > >    
   > > > > Dear Maintainer,   
   > > > >    
   > > > > I've just debugged a new issue with 6.12.69+deb13 vs. 6.12.63+deb13.   
   > > > > chrony 4.6.1 (the version in Debian stable) started failing to start   
   > > > > with "Fatal error : Could not enable external PHC timestamping".   
   > > > >    
   > > > > We use the extpps mode with PTP hardware clocks. It seems that   
   > > > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/l   
   nux.git/commit/?id=97529630d85f910f4e6dfc615f1d111ada9448e3   
   > > > > changes /dev/ptp* to now require FDs open for writing to configure   
   > > > > extpps. Chrony has a fix   
   > > > > (https://gitlab.com/chrony/chrony/-/commit/f78e4681eff71   
   941fab3be5ee406d920a155a20),   
   > > > > but that's only in the version in testing/sid.   
   > > >    
   > > > We talked about this bug on yesterdays team meeting, and it was   
   > > > commented as the kernel change is a security fix, it likely won't be   
   > > > reverted and the fix should be backported for chrony to the affected   
   > > > releases and schedule fixes via the point releases (with ideally the   
   > > > option to make an update as well make it as a SUA to get earlier to   
   > > > users affected by the issue).   
   > >    
   > > Fair!   
   > >     
   > > > Would you be willing to work on those backports and propose the point   
   > > > release updates?   
   > >    
   > > I will handle this. I will provide a build for Jan to test because I do   
   > > not have that kind of setup at hand.   
   >    
   > Jan, could you please test the attached .deb? It includes a backport of   
   > the aforementioned chrony fix and some adjustments to the test suite.   
   >    
   > Cheers,   
   > Vincent   
   >    
   > P.S. sha256sum: b6f253e4429c0efe56429f4a8d9a109897863fa3a83099   
   99bf236ff10bbe253  chrony_4.6.1-3+deb13u1_amd64.deb   
      
      
      
   --nxmHZJvvUC+EC8GY   
   Content-Type: application/vnd.debian.binary-package   
   Content-Disposition: attachment; filename="chrony_4.6.1-3+deb13u1_amd64.deb"   
   Content-Transfer-Encoding: base64   
   [SoupGate killed MIME-encoded file chrony_4.6.1-3+deb13u1_amd64.deb (309968   
   bytes)]   
      
      
   --nxmHZJvvUC+EC8GY--   
      
   -----BEGIN PGP SIGNATURE-----   
      
   iHUEABYKAB0WIQSRJQjHKbAUfuoc+DAQn1qAt/bgAQUCaZNNngAKCRAQn1qAt/bg   
   AXLnAQDtMHBtk1m3e1sf5nZjbDAN6lmghw5rVnHp2e4uLddGAAD/ZOzCa0y8ItR3   
   ioLU2rvfBcDDcfQa03beascCp9UYYAw=   
   =oerK   
   -----END PGP SIGNATURE-----   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)