TL;DR The NTP Code around this is simplified: 1. Complex thing eventually setting ret to next element 2. assert ret!=NULL <-- this is what our bug reports hit
"Complex thing" was completely rewritten in the referred patch set to close the race window that it had. So no matter these NTP bugs refer to slightly other ways of this issue to surface it is very likely the same "race". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1567540 Title: ntpd crashed with SIGABRT (was: ntp crashes everytime the network goes up or down.) To manage notifications about this bug go to: https://bugs.launchpad.net/ntp/+bug/1567540/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
