From: Ben Greear <greearb@candelatech.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Michael Leun <lkml20100708@newton.leun.net>,
Greg KH <greg@kroah.com>,
netdev@vger.kernel.org, davem@davemloft.net,
linux-kernel@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Patrick McHardy <kaber@trash.net>
Subject: Re: NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn)
Date: Thu, 05 Aug 2010 09:57:14 -0700 [thread overview]
Message-ID: <4C5AED6A.8040602@candelatech.com> (raw)
In-Reply-To: <m1y6clz8ta.fsf_-_@fess.ebiederm.org>
On 08/05/2010 02:51 AM, Eric W. Biederman wrote:
> Michael Leun<lkml20100708@newton.leun.net> writes:
>> Unfortunately looks like indefinitely. Never watched longer so far
>> (rebooted soon), but I'm seeing this message now repeated every 10 secs
>> for ~10 minutes on a idle system.
>
> Ugh. A real bug then. These can be a pain to track down and fix. I
> think the last one of these I tracked down took a couple of weeks. I
> will start digging in when I get back from vacation.
I once spent a similar amount of time putting in debug variants that
printed info for each time a netdev was acquired and released.
Maybe a similar logic could be put into the official kernel (and
disabled by default)?
That should save effort in the long run, I'd think.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2010-08-05 16:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <loom.20100708T183152-326@post.gmane.org>
[not found] ` <20100709235744.GA12752@kroah.com>
[not found] ` <20100710101540.2799c9ef@xenia.leun.net>
[not found] ` <20100710140800.GA20424@kroah.com>
[not found] ` <20100710165208.59272ae6@xenia.leun.net>
[not found] ` <20100710235323.5336f627@xenia.leun.net>
2010-07-11 17:29 ` FW: NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn) (was Re: sysfs bug when using tun with network namespaces) Michael Leun
2010-08-04 13:35 ` Michael Leun
2010-08-04 21:46 ` Greg KH
2010-08-04 22:04 ` NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn) Eric W. Biederman
2010-08-04 22:11 ` NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn) (was Re: sysfs bug when using tun with network namespaces) Michael Leun
2010-08-05 0:12 ` Eric W. Biederman
2010-08-05 9:25 ` Michael Leun
2010-08-05 9:51 ` NET_NS: unregister_netdevice: waiting for lo to become free (after using openvpn) Eric W. Biederman
2010-08-05 10:13 ` Michael Leun
2010-08-05 11:47 ` NET_NS: unregister_netdevice: waiting for lo to become free (adding ipv6 address to interface) Michael Leun
2010-08-05 19:57 ` Eric W. Biederman
2010-08-05 20:11 ` David Miller
2010-08-05 23:45 ` lkml20100708
2010-08-06 0:09 ` Michael Leun
2010-10-21 15:15 ` Michael Leun
2010-10-22 12:48 ` David Lamparter
2010-10-22 17:05 ` Michael Leun
2010-10-24 13:15 ` Michael Leun
2010-12-06 16:08 ` Menil Jean-Philippe
2010-12-06 21:22 ` Eric W. Biederman
2010-12-06 22:47 ` Michael Leun
2010-12-07 10:40 ` Menil Jean-Philippe
2010-08-05 16:57 ` Ben Greear [this message]
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=4C5AED6A.8040602@candelatech.com \
--to=greearb@candelatech.com \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml20100708@newton.leun.net \
--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;
as well as URLs for NNTP newsgroup(s).