search for: unregister_netdevice

...is a refcount release problem, it should appear on eavy = load (some buffer overflow, or something like that). Also, are you playing with ebtables? How do you use this bridge? #Louis. Date: Wed, 31 Aug 2005 19:04:01 -0700 > From: Robert Scott <rbscott@axentra.net> > Subject: [Bridge] unregister_netdevice: waiting for br0 to become > free. Usage count =3D 1 (2.6.12.3 <http://2.6.12.3/>) > To: bridge@lists.osdl.org > Message-ID: <8189B9F5-DF6E-4032-8D2D-D5301A02A081@axentra.net> > Content-Type: text/plain; charset=3DUS-ASCII; delsp=3Dyes; format=3Dflowed > = > Hello, &g...

Hi list, I use xen-unstable download by hg on 8.24, i create a guest os "freedos", it just display a black screen. Then i destroy the guest os by "xm destroy",I closed. And then message jump out: =========================================== localhost kernel:unregister_netdevice:waiting for tun0 to became free. Usage count=1 Message from syslogd@localhost at Fri Aug 26 06:53:40 2005 ... localhost last message repeated 7 times. localhost last message repeated 6 times. localhost last message repeated 6 times. ... =========================================== The xend-debug.l...

...ce I got no feedback from devel list. Hope someone can help. Thanks in advance. Huaxiang From: xen-devel-bounces@lists.xensource.com [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Fan, Huaxiang Sent: Friday, July 22, 2011 2:51 PM To: xen-devel@lists.xensource.com Subject: [Xen-devel] unregister_netdevice:waiting for vifXXX.0 to become free. Usage count =1 Hi, This message is showed in /var/log/messages on dom0 when I am trying to shutdown a domu. Sometime it can shutdown eventually, sometime it hang forever. Sometimes, it can shutdown smoothly even without this message. i.e., We can not stably re...

...ello guys I have the following problem with xen 3.0.1 compiled from sources on Debian Sarge, kernel 2.6.12.6 which can be easily reproduced at least on my installation: after I log in to domU console or via ssh and run "shutdown" I get deadlocked network interface with error message: unregister_netdevice: waiting for vifX.0 to become free. Usage count = n After this happen I can''t even reboot my dom0 via ssh because reboot process hangs (waits until interface is released but it never happens). I googled about this error and found some references to bridged networking problem (yes I use...

Hi, This message is showed in /var/log/messages on dom0 when I am trying to shutdown a domu. Sometime it can shutdown eventually, sometime it hang forever. Sometimes, it can shutdown smoothly even without this message. i.e., We can not stably reproduce this problem but we encounter this problem several times in total. I enable IPv6 on both dom0 and domu. I google it a little, it seems related to

...utput: https://syzkaller.appspot.com/x/log.txt?x=126de6f1280000 IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+881d65229ca4f9ae8c84 at syzkaller.appspotmail.com Fixes: ad2f99aedf8f ("net: bridge: move bridge ioctls out of .ndo_do_ioctl") unregister_netdevice: waiting for bridge0 to become free. Usage count = 2 leaked reference. __netdev_tracker_alloc include/linux/netdevice.h:4070 [inline] netdev_hold include/linux/netdevice.h:4099 [inline] dev_ifsioc+0xbc0/0xeb0 net/core/dev_ioctl.c:408 dev_ioctl+0x250/0x1090 net/core/dev_ioctl.c:605 sock_do_ioct...

...; if (tun) { > - DBG(KERN_INFO "%s: tun_chr_close\n", tun->dev->name); > - > - rtnl_lock(); > - __tun_detach(tun); > - > /* If desireable, unregister the netdevice. */ > - if (!(tun->flags & TUN_PERSIST)) { > - sock_put(tun->sk); > - unregister_netdevice(tun->dev); > - } > + if (!(tun->flags & TUN_PERSIST)) > + unregister_netdev(tun->dev); > + else > + tun_put(tun); > + } else > + tun = tfile->tun; > > - rtnl_unlock(); > + if (tun) { > + DBG(KERN_INFO "%s: tun_chr_close\n", tun-...

...; if (tun) { > - DBG(KERN_INFO "%s: tun_chr_close\n", tun->dev->name); > - > - rtnl_lock(); > - __tun_detach(tun); > - > /* If desireable, unregister the netdevice. */ > - if (!(tun->flags & TUN_PERSIST)) { > - sock_put(tun->sk); > - unregister_netdevice(tun->dev); > - } > + if (!(tun->flags & TUN_PERSIST)) > + unregister_netdev(tun->dev); > + else > + tun_put(tun); > + } else > + tun = tfile->tun; > > - rtnl_unlock(); > + if (tun) { > + DBG(KERN_INFO "%s: tun_chr_close\n", tun-...

Hello, I have two hosts with a tunnel closed by vtun, when I reboot a host, the other show the error bellow. unregister_netdevice: waiting for tun0 to become free. Usage count = 6 OS version: CentOS 5.4 Vtund version: vtun-3.0.2-1 some idea about? Thanks -- Daniel Bruno http://danielbruno.eti.br danielbruno at projetofedora.org

When i want to delete my test bridge, using: ifconfig eth0 down ifconfig eth1 down ifconfig br0 down brctl delif br0 eth0 brctl delif br0 eth1 brctl delbr br0 i get this error message from the kernel on the console: unregister_netdevice: waiting for br0 to become free. Usage count =3D 2 The brctl user-level command is blocked. Could you explain me what could likely be the cause of this error? Thanks in advance, #Louis. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.linux-foundation.o...

...riencing a minor problem using the bridge module under kernel 2.4.27 part of the Devil Linux distribution (http://www.devil-linux.org). The problem I am having is that when the bridge is unloaded during a reboot I receive the following errors in /var/log/messages: Nov 14 13:22:13 src@Devil kernel: unregister_netdevice: waiting for br0 to become free. Usage count = 2 This message is repeatedly output to the console until I manually go and power cycle it. I've traced this through the startup/shutdown scripts, and have determine that the problem exists in the following sequence of commands: brctl addbr br0 br...

With recent 2.6 kernels, the command brctl delbr br0 hangs during shutdown, and the kernel prints this message again and again: unregister_netdevice: waiting for br0 to become free. Usage count = 1 I was able to reproduce this problem with several kernels between (and including) 2.6.9-rc1 and 2.6.11-rc2-bk9. I haven't tried later versions than 2.6.11-rc2-bk9 yet. 2.6.8.1-bk2 still works fine. My .config was taken from the Debian kernel-i...

...t; leaked reference created by race conditions in dev_ioctl, specifically, > under SIOCBRADDIF or SIOCBRDELIF operations. The reference leak would How would it leak a reference, could you elaborate? The reference is always taken and always released after the call. > be shown in the periodic unregister_netdevice call, which throws a > warning and cause Syzbot to report a crash. Upon inspection of the If you reproduced it, is the device later removed or is it really stuck? > logic in dev_ioctl, it seems the reference was introduced to ensure > proper access to the bridge device after rtnl_unlock....

In the bug reported by Syzbot, certain bridge devices would have a leaked reference created by race conditions in dev_ioctl, specifically, under SIOCBRADDIF or SIOCBRDELIF operations. The reference leak would be shown in the periodic unregister_netdevice call, which throws a warning and cause Syzbot to report a crash. Upon inspection of the logic in dev_ioctl, it seems the reference was introduced to ensure proper access to the bridge device after rtnl_unlock. and the latter function is necessary to maintain the following lock order in any bridge r...

...in the VM, so I'd say it did not > get stuck. > >> How would it leak a reference, could you elaborate? >> The reference is always taken and always released after the call. > > This was where I got a bit confused too. The system had a timeout of > 140 seconds for the unregister_netdevice check. If the bridge in > question was created and deleted repeatedly, the warning would indeed > not be an actual reference leak. But how could its reference show up > after 140 seconds if the bridge's creation and deletion were all within > a couple of milliseconds? > > So...

...up when I polled with `ip link` in the VM, so I'd say it did not get stuck. > How would it leak a reference, could you elaborate? > The reference is always taken and always released after the call. This was where I got a bit confused too. The system had a timeout of 140 seconds for the unregister_netdevice check. If the bridge in question was created and deleted repeatedly, the warning would indeed not be an actual reference leak. But how could its reference show up after 140 seconds if the bridge's creation and deletion were all within a couple of milliseconds? So I let the system run for a bit...

...the circular lock dependency, where, for example, the current thread already locks j1939_socks_lock and attempts to acquire sk_session_queue_lock, and at the same time, another thread attempts to acquire j1939_socks_lock while holding sk_session_queue_lock. NOTE: This patch along does not fix the unregister_netdevice bug reported by Syzbot; instead, it solves a deadlock situation to prepare for one or more further patches to actually fix the Syzbot bug, which appears to be a reference counting problem within the j1939 codebase. Reported-by: syzbot+1591462f226d9cbf0564 at syzkaller.appspotmail.com Signed-off-by...

...n, ...] List information about all/some domains. -l, --long Output all VM details in SXP --label Include security labels root@ben1-desktop:/etc/xen# Message from syslogd@ben1-desktop at Mon Jul 16 19:31:59 2007 ... ben1-desktop kernel: [82878.270011] unregister_netdevice: waiting for vif2.0 to become free. Usage count = 18236 -- View this message in context: http://www.nabble.com/Error%3A-Device-0-not-connected%2C-waiting-for-vif2.0-to-become-free.-Usage-count-%3D-18236-tf4190906.html#a11918098 Sent from the Xen - User mailing list archive at Nabble.com. ______...

...verts parts of xen-unstable c/s 9019:271cb04a4f2b [1] [2] (though that has a typo: "__init clean_loopback", so it was probably changed later too). The patch fixes the problem of "rmmod netloop" hanging, resulting in blocked tasks and inability to shut down cleanly: ... kernel: unregister_netdevice: waiting for veth4 to become free. Usage count = 1 The problem was also reported for Debian [3] and on the Fedora-xen mailing list [4]. Thanks for considering, lacos [0] https://bugzilla.redhat.com/show_bug.cgi?id=567540 [1] http://lists.xensource.com/archives/html/xen-devel/2006-02/msg01033.htm...

...State Time(s) Domain-0 0 1748 2 r----- 29396.3 xp-101 1 256 1 -b---- 4685.8 [**@xentest ::三 12月 21::~]$ sudo xm save 1 1.save Message from syslogd@ at Wed Dec 21 10:27:10 2011 ... xentest kernel: unregister_netdevice: waiting for tap1.0 to become free. Usage count = 1 Message from syslogd@ at Wed Dec 21 10:27:41 2011 ... xentest last message repeated 3 times Message from syslogd@ at Wed Dec 21 10:28:52 2011 ... xentest last message repeated 7 times ....................... ------------------ 原始邮件 -------...