Hi Dan,

> There's actually been quite a lot of discussion/work in this bug since 
> comment 2, so I don't 
> actually need that info anymore (except for reproduction steps, that's always 
> welcome).

Fair enough. I wish I had some reproduction steps but unfortunately it
just happens randomly and not because of any one action.

> Are you having any problems with the system *other* than just the log
messages?

Apologies here. I should have mentioned how it affects us. The symptoms
seen are a number of docker commands that just hang indefinitely (e.g.
docker ps, spinning up new containers). Occasionally, after a long time,
we have seen it come back and continue working OK (like whatever was
holding the lock released it finally), but most of the time it hangs
indefinitely. On occasion we can also use the -n parameter (e.g. docker
ps -n #) and it may or may not return a partial listing of running
containers. We've also found (again, not always) that we might be able
to stop a container if we use the container name or ID. When we strace
the process, we just see:

write(5, "GET /v1.24/containers/json?limit"..., 97) = 97
futex(0xc8200fa590, FUTEX_WAKE, 1)      = 1
futex(0x21fce50, FUTEX_WAIT, 0, NULL

... and that's as far as it goes. I do have a Docker stacktrace if you
want to see that.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1711407

Title:
  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.

  --

  [Impact]

  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 =
  1

  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-
  samba-loop

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

-- 
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