While I can visually confirm that the fix in comment #10 is now in the
zesty source code (and the fix is not in the xenial/yakkety source
code), I'm unable to actually recreate the experience of a valgrind
failure on xenial (I've attempted with both i386 and amd64 xenial
containers). I additionally rebuilt the amd64 source with -O0 -g but
that did not affect the valgrind run as well.
Reporter, can you trigger this bug on the Ubuntu Xenial (16.04)? To get
this accepted through the SRU approval process we should really have
some testcase that actually triggers the issue.
root@x2:~# ip -V
ip utility, iproute2-ss151103
root@x2:~# valgrind ip netns add black2
==916== Memcheck, a memory error detector
==916== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==916== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==916== Command: ip netns add black2
==916==
==916==
==916== HEAP SUMMARY:
==916== in use at exit: 0 bytes in 0 blocks
==916== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==916==
==916== All heap blocks were freed -- no leaks are possible
==916==
==916== For counts of detected and suppressed errors, rerun with: -v
==916== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
root@x2:~#
So where this sits:
1) Appears fixed in zesty
2) Needs a testcase/recreate scenario if desired fixed in Yakkety/Xenial
** Changed in: iproute2 (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1615209
Title:
ip crashes after a few times adding and removing network namespaces
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1615209/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
