netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tommi Rantala <tommi.t.rantala@nokia.com>
To: Vlad Yasevich <vyasevich@gmail.com>,
	Neil Horman <nhorman@tuxdriver.com>,
	linux-sctp@vger.kernel.org,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: sctp netns "unregister_netdevice: waiting for lo to become free. Usage count = 1"
Date: Mon, 29 Jan 2018 17:55:45 +0200	[thread overview]
Message-ID: <2a9c25b0-9ee7-baf6-f212-2c94b06941ea@nokia.com> (raw)

Hi,

When running sctp_test from lksctp-tools in netns in 4.4 and 4.9 with 
suitable arguments, the local loopback device in the netns is not 
getting destroyed after deleting the netns.

For example:

ip netns add TEST
ip netns exec TEST ip link set lo up
ip link add dummy0 type dummy
ip link add dummy1 type dummy
ip link add dummy2 type dummy
ip link set dev dummy0 netns TEST
ip link set dev dummy1 netns TEST
ip link set dev dummy2 netns TEST
ip netns exec TEST ip addr add 192.168.1.1/24 dev dummy0
ip netns exec TEST ip link set dummy0 up
ip netns exec TEST ip addr add 192.168.1.2/24 dev dummy1
ip netns exec TEST ip link set dummy1 up
ip netns exec TEST ip addr add 192.168.1.3/24 dev dummy2
ip netns exec TEST ip link set dummy2 up
ip netns exec TEST sctp_test -H 192.168.1.2 -P 20002 -h 192.168.1.1 -p 
20000 -s -B 192.168.1.3
ip netns del TEST

Results to:

[  354.179591] unregister_netdevice: waiting for lo to become free. 
Usage count = 1
[  364.419674] unregister_netdevice: waiting for lo to become free. 
Usage count = 1
[  374.663664] unregister_netdevice: waiting for lo to become free. 
Usage count = 1
[  384.903717] unregister_netdevice: waiting for lo to become free. 
Usage count = 1
[  395.143724] unregister_netdevice: waiting for lo to become free. 
Usage count = 1
[  405.383645] unregister_netdevice: waiting for lo to become free. 
Usage count = 1
...

Based on a quick test, 4.14 and 4.15 does not suffer from this, but its 
reproducible e.g. in 4.4.113 and 4.9.75

Any ideas?

Tommi

             reply	other threads:[~2018-01-29 15:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 15:55 Tommi Rantala [this message]
2018-01-30 15:59 ` sctp netns "unregister_netdevice: waiting for lo to become free. Usage count = 1" Neil Horman
2018-01-30 19:24   ` Tommi Rantala
2018-01-30 21:03     ` Neil Horman
2018-01-31  9:42       ` Tommi Rantala
2018-01-31 12:13         ` Tommi Rantala
2018-01-31 12:31         ` Neil Horman
2018-01-31 17:51           ` Tommi Rantala
2018-02-01 18:02             ` Tommi Rantala
2018-02-01 19:23               ` Neil Horman
2018-02-01 20:41                 ` Tommi Rantala
2018-02-02 12:34                   ` Neil Horman
2018-02-04  9:05                     ` Tommi Rantala
2018-02-01 23:57               ` Alexey Kodanev
2018-02-02  8:27                 ` Tommi Rantala
2018-02-02 12:17                   ` Alexey Kodanev
2018-01-30 22:52 ` Marcelo Ricardo Leitner
2018-01-31  6:58   ` Tommi Rantala

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=2a9c25b0-9ee7-baf6-f212-2c94b06941ea@nokia.com \
    --to=tommi.t.rantala@nokia.com \
    --cc=linux-sctp@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@tuxdriver.com \
    --cc=vyasevich@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).