On Mon, Apr 23, 2018 at 8:01 PM, Tiainen, Antti <atiainen(a)forcepoint.com> wrote:
Strange, it doesn't crash for me if I try your example. But if I
your patch, the deleted interface just hangs there in ifinfo list forever,
even when change handlers are called.
If this is only a debug print issue, it cannot do simply NULL check in
there, and print something (or nothing) for the interface that's completely
I don't think so, as said in the changelog, that's the dbg log
which delays the destruction, so that it can show a nice info to users
when removing a port.
Not only here like that, but also in the team_port's destruction.
-1450: veth1: down 0Mbit HD <--
The similar process is also used on the team_port's destruction.
So far, that's a 'not bad' way I could see, maybe you have a better fix