From: Eyal Birger <eyal.birger@gmail.com>
To: steffen.klassert@secunet.com
Cc: netdev@vger.kernel.org, herbert@gondor.apana.org.au,
davem@davemloft.net, shmulik@metanetworks.com
Subject: Re: xfrm, ip tunnel: non released device reference upon device unregistration
Date: Sun, 4 Feb 2018 15:32:52 +0200 [thread overview]
Message-ID: <20180204153252.29b4c982@jimi> (raw)
In-Reply-To: <20180204132118.6fef9bf0@jimi>
On Sun, 4 Feb 2018 13:21:18 +0200
Eyal Birger <eyal.birger@gmail.com> wrote:
> Hi,
>
> We've encountered a non released device reference upon device
> unregistration which seems to stem from xfrm policy code.
>
> The setup includes:
> - an underlay device (e.g. eth0) using IPv4
> - an xfrm IPv6 over IPv4 tunnel routed via the underlay device
> - an ipip6 tunnel over the xfrm IPv6 tunnel
>
> When tearing down the underlay device, after traffic had passed via
> the ipip6 tunnel, log messages of the following form are observed:
>
> unregister_netdevice: waiting for eth0 to become free. Usage count = 2
>
> The below synthetic script reproduces this consistently on a fresh
> ubuntu vm running net-next v4.15-6066-ge9522a5:
Minor correction: net-next version v4.15-10442-g617aebe
Eyal.
next prev parent reply other threads:[~2018-02-04 13:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 11:21 xfrm, ip tunnel: non released device reference upon device unregistration Eyal Birger
2018-02-04 13:32 ` Eyal Birger [this message]
2018-02-06 8:53 ` Steffen Klassert
2018-02-06 10:32 ` Florian Westphal
2018-02-06 10:42 ` Eyal Birger
2018-02-06 12:56 ` Florian Westphal
2018-02-06 13:09 ` Steffen Klassert
2018-02-06 13:15 ` Florian Westphal
2018-02-06 13:21 ` Steffen Klassert
2018-02-06 19:19 ` Eyal Birger
2018-02-11 15:46 ` Florian Westphal
2018-02-12 11:54 ` Eyal Birger
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=20180204153252.29b4c982@jimi \
--to=eyal.birger@gmail.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=shmulik@metanetworks.com \
--cc=steffen.klassert@secunet.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).