netdev - linux-next: next-20160301: unregister_netdevice: waiting for lo to become free. Usage count = 2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 1 Mar 2016 08:11:54 +0000
From:	Dexuan Cui <decui@...rosoft.com>
To:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC:	Haiyang Zhang <haiyangz@...rosoft.com>
Subject: linux-next: next-20160301: unregister_netdevice: waiting for lo to
 become free. Usage count = 2

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 be a recent regression, as I remember the January linux-next didn't have
this issue.

Any idea?

The gzip-ed kernel config is attached FYI.

Thanks,
-- Dexuan

Download attachment "kernel.config.gz" of type "application/x-gzip" (46145 bytes)