Re: libnl bug.

[Thomas Graf <tgraf suug ch>]

Robert,

>         Program received signal SIGSEGV, Segmentation fault.
>         [Switching to Thread 1077037344 (LWP 30554)]
>         0x4004a43d in rtnl_link_build_change_request (old=0x0, tmpl=0x80887f0, flags=0)
>             at link.c:752
>         752     link.c: No such file or directory.
>                 in link.c
>         (gdb) bt
>         #0  0x4004a43d in rtnl_link_build_change_request (old=0x0, tmpl=0x80887f0,
>             flags=0) at link.c:752
>         #1  0x4004a706 in rtnl_link_change (handle=0x8087030, old=0x0, tmpl=0x80887f0,
>             flags=0) at link.c:812

If this backtrace is correct then this is not a libnl bug but rather
a illegal use of the interface. What link do you expect to be changed
with old=0x0?

`old' is supposed to point to the link subject to be changed, `tmpl'
must contain the attributes to be changed. This separation is required
because the kernel interface allows the to be changed link being
identified by name or by index. Typically `old' points to a link object
out of a cache but may also just contain the ifindex or name attribute
the latter preventing the interface name to be changed.