dev-lib/libnl-3.2.17 makes networkmanager (presumably on an ipv6-enabled network) segfault like this: #0 0x0000000000000000 in ?? () #1 0x00007ffff770d818 in cache_include (data=0x0, cb=0x0, obj=0x78b8b0, cache=0x709950, type=<optimized out>) at cache.c:755 #2 nl_cache_include (cache=0x709950, obj=0x78b8b0, change_cb=0x0, data=0x0) at cache.c:799 #3 0x000000000047e51b in process_route_change (msg=<optimized out>, manager=0x772d90) at nm-ip6-manager.c:935 #4 netlink_notification (monitor=<optimized out>, msg=<optimized out>, user_data=0x772d90) at nm-ip6-manager.c:1355 libnl-3.2.16 works fine. Line 755 of cache.c is the call to "cb", for which networkmanager passed NULL (see nm-ip6-manager.c:935). Adding the obvious null check (present in other branches in the same function) to libnl makes everything go again. This should be reported upstream, but if I'm right about this breaking all networkmanagers on ipv6-enabled networks consider patching gentoo's libnl or masking 3.2.17. Corroborating evidence: 3.2.17 contains a fix for the next line of the same codepath missing this null check, with the commit message mentioning "None of the caches have support for object update, so this should not have affected anyone yet." (which explains the missing null check not breaking networkmanager in 3.2.16: this codepath was never hit), and the next change says it "adds search and replace/update functionality to cache pickup_cb" (which I'm guessing made the codepath live).
Oh dear, again a libnl issue that breaks NetworkManager ? I hit this bug as well I think. Perhaps more testing should be involved before making random updates to (obviously) totally broken libnl updates ...
Oh, there we go again. :)
3.2.18 is in the tree and 3.2.17 is gone: mihai.dontu@gmail.com (1): cache: make sure the user has specified a callback
