From: David Ahern <dsa@cumulusnetworks.com>
To: Jeremiah Mahler <jmmahler@gmail.com>,
Dexuan Cui <decui@microsoft.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Haiyang Zhang <haiyangz@microsoft.com>,
"David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION, bisect] net: ipv6: unregister_netdevice: waiting for lo to become free. Usage count = 2
Date: Wed, 2 Mar 2016 13:00:21 -0800 [thread overview]
Message-ID: <56D75465.4060705@cumulusnetworks.com> (raw)
In-Reply-To: <20160302203150.GA2045@hudson.localdomain>
On 3/2/16 12:31 PM, Jeremiah Mahler wrote:
>> On Tue, Mar 01, 2016 at 08:11:54AM +0000, Dexuan Cui wrote:
>>> Hi, I got this line every 10 seconds with today's linux-next in a Hyper-V guest, even
>>> when I didn't configure any NIC for the guest:
>>>
>>> [ 72.604249] unregister_netdevice: waiting for lo to become free. Usage count = 2
>>> [ 82.708170] unregister_netdevice: waiting for lo to become free. Usage count = 2
>>> [ 92.788079] unregister_netdevice: waiting for lo to become free. Usage count = 2
>>> [ 102.808132] unregister_netdevice: waiting for lo to become free. Usage count = 2
>>> [ 112.928166] unregister_netdevice: waiting for lo to become free. Usage count = 2
>>> [ 122.952069] unregister_netdevice: waiting for lo to become free. Usage count = 2
>>>
>>> I don't think this is related to the underlying host, since it's related to "lo".
This should fix it:
https://patchwork.ozlabs.org/patch/591102/
David
next prev parent reply other threads:[~2016-03-02 21:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6c735168f53548a39bd21e6e9857f512@HKXPR3004MB0088.064d.mgd.msft.net>
[not found] ` <20160301200749.GA1611@hudson.localdomain>
2016-03-02 20:31 ` [REGRESSION, bisect] net: ipv6: unregister_netdevice: waiting for lo to become free. Usage count = 2 Jeremiah Mahler
2016-03-02 21:00 ` David Ahern [this message]
2016-03-03 1:23 ` Jeremiah Mahler
2016-03-03 5:25 ` Dexuan Cui
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=56D75465.4060705@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=jmmahler@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox