← Back to team overview

desktop-packages team mailing list archive

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


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?

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?

> To summarize, if an application on the system chooses manually a port
id (because it does not use the libnl or because it sets it manually),
it may conflict with applications that use libnl and prevent them to
work properly.

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?

You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.

  libnl: fail to bind() netlink sockets

Status in libnl3 package in Ubuntu:
  Fix Released
Status in libnl3 source package in Trusty:

Bug description:
  The following upstream patches are needed in order to avoid failures
  when binding a netlink socket:

  1f734a8f892a lib/socket: randomize the generated local port

  4dd5fdd0af2c lib/socket: retry generate local port in nl_connect on ADDRINUSE

  027157898708 lib/socket: don't fail if no more local ports can be assigned in nl_socket_alloc

  0fd510b3673f lib/socket: use proper typed constant UINT32_MAX for uint32_t typed port

  Without these patches, an application which opens and closes regularly
  netlink sockets can easily fails to bind them.

To manage notifications about this bug go to: