All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Andrey Wagin <avagin@gmail.com>, netdev@vger.kernel.org
Subject: Re: [net-next,v7] net: ipv6: Make address flushing on ifdown optional
Date: Wed, 2 Mar 2016 10:23:17 -0800	[thread overview]
Message-ID: <56D72F95.3030101@gmail.com> (raw)
In-Reply-To: <CANaxB-z7JefW0hQ2cODX_JLOqWbpTM371E_SDpGXrmdtvS_UcA@mail.gmail.com>

On 3/2/16 10:01 AM, Andrey Wagin wrote:
> Hi David,
>
> We execute CRIU test on linux-next. On the current linux-next kernel
> they hangs on creating a network namespace.
>
> The kernel log contains many massages like this:
> [ 1036.122108] unregister_netdevice: waiting for lo to become free.
> Usage count = 2
> [ 1046.165156] unregister_netdevice: waiting for lo to become free.
> Usage count = 2
> [ 1056.210287] unregister_netdevice: waiting for lo to become free.
> Usage count = 2
>
> I tried to revert this patch and the bug disappeared.
>
> Here is a set of commands to reproduce this bug:
>
> [root@linux-next-test linux-next]# uname -a
> Linux linux-next-test 4.5.0-rc6-next-20160301+ #3 SMP Wed Mar 2
> 17:32:18 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> [root@linux-next-test ~]# unshare -n
> [root@linux-next-test ~]# ip link set up dev lo
> [root@linux-next-test ~]# ip a
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> group default qlen 1
>      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
>      inet 127.0.0.1/8 scope host lo
>         valid_lft forever preferred_lft forever
>      inet6 ::1/128 scope host
>         valid_lft forever preferred_lft forever
> [root@linux-next-test ~]# logout
> [root@linux-next-test ~]# unshare -n

Thanks for reporting -- with reproduction commands. I will post patch as 
soon as I have time to look into it.

David

      reply	other threads:[~2016-03-02 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-02 18:01 [net-next,v7] net: ipv6: Make address flushing on ifdown optional Andrey Wagin
2016-03-02 18:23 ` David Ahern [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56D72F95.3030101@gmail.com \
    --to=dsahern@gmail.com \
    --cc=avagin@gmail.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.