Bug#795315: /usr/sbin/ntpd: ntpd segfaults in input_handler at ntp_io.c:3642

Version: 1:4.2.8p3+dfsg-1 On Thu, Aug 13, 2015 at 12:08:23AM +0200, Bjørn Mork wrote: > Package: ntp > Version: 1:4.2.6.p5+dfsg-7 > Followup-For: Bug #795315 > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Dear Maintainer, > > well, that was easy. This bug was fixed by upstream

Bug#795315: /usr/sbin/ntpd: ntpd segfaults in input_handler at ntp_io.c:3642

Package: ntp Version: 1:4.2.6.p5+dfsg-7 Severity: important File: /usr/sbin/ntpd -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, Lately I've had repeated segfaults at the same strange instruction pointer. Some examples: [413548.161658] ntpd[10451]: segfault at 31 ip

Bug#795315: /usr/sbin/ntpd: ntpd segfaults in input_handler at ntp_io.c:3642

Package: ntp Version: 1:4.2.6.p5+dfsg-7 Followup-For: Bug #795315 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, looking a bit further at the code, I believe I now understand what goes wrong: The process_routing_msgs(), which is called indirectly inside the list loopi, could end

Bug#795315: /usr/sbin/ntpd: ntpd segfaults in input_handler at ntp_io.c:3642

Package: ntp Version: 1:4.2.6.p5+dfsg-7 Followup-For: Bug #795315 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dear Maintainer, well, that was easy. This bug was fixed by upstream several years ago. Attaching patch from upstream. Bjørn - -- System Information: Debian Release: 8.1 APT