** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
       Status: Confirmed

** Tags added: bionic kernel-da-key

** Changed in: linux (Ubuntu Bionic)
       Status: Confirmed => Triaged

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

  rtnetlink: enable namespace identifying properties in rtnetlink

Status in linux package in Ubuntu:
Status in linux source package in Bionic:

Bug description:

  I've recently pushed a couple of patches to enable IFLA_IF_NETNSID to
  be passed in rtnetlink requests to avoid having to take the hit of
  setns() to a network namespace and its owning user namespace when
  performing operations on a target network namespace. This makes a lot
  of costly operations for LXD through liblxc way cheaper. Juju is one
  candidate that recently suffered from costs caused by lxc list on a
  LXD instance with a lot of containers. If it's not too much trouble in
  the current meltdown/spectre and pre-LTS release craziness it would be
  really great if we could ensure that these patches make it into the
  Bionic kernel and possibly be backported to the 16.04 kernel. The
  16.04 kernel might be a little annoying though since it misses a few
  pre-requisite patches but if you think that we can do it I can give
  you the patches that you need to make it easier for you! Here are the
  patches that are required for 4.15 in Bionic:






  There's one additional (security/hardening) patch which has been acked
  and will very likely make it into 4.16 as well once Dave picks it up
  and sends it to Linus. So I'm listing it here right away but if you
  want to wait until it is fully upstream, I understand:



To manage notifications about this bug go to:

Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to