Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752895AbcCBVA0 (ORCPT ); Wed, 2 Mar 2016 16:00:26 -0500 Received: from mail-pf0-f172.google.com ([209.85.192.172]:33275 "EHLO mail-pf0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751535AbcCBVAY (ORCPT ); Wed, 2 Mar 2016 16:00:24 -0500 Subject: Re: [REGRESSION, bisect] net: ipv6: unregister_netdevice: waiting for lo to become free. Usage count = 2 To: Jeremiah Mahler , Dexuan Cui , "netdev@vger.kernel.org" , Haiyang Zhang , "David S. Miller" , linux-kernel@vger.kernel.org References: <6c735168f53548a39bd21e6e9857f512@HKXPR3004MB0088.064d.mgd.msft.net> <20160301200749.GA1611@hudson.localdomain> <20160302203150.GA2045@hudson.localdomain> From: David Ahern Message-ID: <56D75465.4060705@cumulusnetworks.com> Date: Wed, 2 Mar 2016 13:00:21 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <20160302203150.GA2045@hudson.localdomain> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 946 Lines: 19 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