> I have just reproduced it using the previous #43+hf1711407v20180412b2"

Excellent.  And just to clarify again, I do *not* expect the kernel to
fix/avoid the problem - I fully expect it to happen - the change in
these kernels is strictly to make sure that the system is still usable
after the problem happens.  Can you verify that after reproducing?  I
assume that before, when you reproduced the problem, you were no longer
able to create new (or destroy old) containers (i.e., new net
namespaces) - that should now be fixed, and you should be able to keep
creating new containers with no issues.

> The seconds seems to be rather milliseconds.

yep sorry, kernel building now should fix that to print seconds instead
of ms.

> Waiting here for the newest kernel and will try it right away.


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

  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.



  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

      unregister_netdevice: waiting for lo to become free. Usage count =

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-

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