1. No, my skills are just not enough to spot it. I noticed warning in valgrind (but it was once only and not crash), but was not able to trace back reason. Very likely your patch fix that.
2. In my network i have some MDNS devices, and probably some combination of them and their connectivity (power failures, packetloss) triggering this bug from time to time. I run back now valgrind with timestamps and will record all port 53 traffic, maybe i can catch pattern. If you want i can apply your patch and do the same. To find the reason i just disabled systemd-resolved service and run manually valgrind -v /lib/systemd/systemd-resolved. Probably other users complained about resolved segfault messages in dmesg and have it happening more often? 3. I was not able to find way to reproduce bug reliably. And now it might take about a week to spot this remaining bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
