[Bug 1511735] Re: libnl: fail to bind() netlink sockets

[Nicolas Dichtel]

>Thank you for your response. It looks like this is fixed in Wily then,
which is on 3.2.26, so this bug affects 14.04 only?

Yes.

>I'm concerned that this changes library behaviour. How can we be sure
that no existing users of libnl will not be regressed by this change in
behaviour if we backport this to 14.04?

This does not change the library behavior. It fixes a real bug. Without this fix, the user has to manage the port id itself. And the only consequence is to increase the probability to show the bug in another application. It's a domino effect. There is two options:
1/ patching all applications that use the libnl
2/ fixing the libnl

>Thanks, this is useful. But can you take us through to actual user
impact of this bug, please? I'm sure you have a concrete case for
wanting this, but so far this explanation is hypothetical. In what
concrete case on 14.04 does an application manually chose a port id that
then causes a conflict and causes a problem for a user?

Yes, I have a concrete case, but it's with a non FOSS application. It's not hypothetical, we hit the bug regularly. And as explained above, trying to fix the impacted applications is a wasted effort because it increases the probability to show the bug in another applications.
FWIW, these patches have been backported by redhat, you can found more info about this bug here:
https://bugzilla.redhat.com/show_bug.cgi?id=1249158

** Bug watch added: Red Hat Bugzilla #1249158
   https://bugzilla.redhat.com/show_bug.cgi?id=1249158

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1511735

Title:
  libnl: fail to bind() netlink sockets

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+subscriptions