On 11/18/2015 10:36 PM, Stefan Priebe wrote: >> please try to get a backtrace with debugging information. It is likely >> that this is the make_request/__check_pf functionality in glibc, but it >> would be nice to get some certainty. > > sorry here it is. What I'm wondering is why is there ipv6 stuff? I don't > have ipv6 except for link local.
glibc needs to know if the system has global unicast addresses if it receives AAAA records. It's curious that net.ipv6.conf.all.disable_ipv6=1 makes the problem go away. Even with that setting, the kernel seems to send two Netlink responses. So either this is enough to narrow the window for the race so that no longer triggers, or there is a genuine kernel issue with supplying the requested IPv6 Netlink response. > Could it be this one? > > https://bugzilla.redhat.com/show_bug.cgi?id=505105#c79 No, that's on the DNS/UDP side, not in the Netlink code. Florian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/