From: ebiederm@xmission.com (Eric W. Biederman)
To: Hans Schillstrom <hans@schillstrom.com>
Cc: Julian Anastasov <ja@ssi.bg>, Simon Horman <horms@verge.net.au>,
netdev@vger.kernel.org, lvs-devel@vger.kernel.org
Subject: Re: unregister_netdevice: waiting for lo to become free. Usage count = 8
Date: Fri, 15 Apr 2011 00:27:20 -0700 [thread overview]
Message-ID: <m1d3ko9dpj.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <201104150901.47214.hans@schillstrom.com> (Hans Schillstrom's message of "Fri, 15 Apr 2011 09:01:46 +0200")
Hans Schillstrom <hans@schillstrom.com> writes:
> Hello Julian
>
> I'm trying to fix the cleanup process when a namespace get "killed",
> which is a new feature for ipvs. However an old problem appears again
>
> When there has been traffic trough ipvs where the destination is unreachable
> the usage count on loopback dev increases one for every packet....
> I guess thats because of this rule :
>
> # ip route list table all
> ...
> unreachable default dev lo table 0 proto kernel metric 4294967295 error -101 hoplimit 25
> ...
>
> I made a test just forwarding packets through the same container (ipvs loaded)
> to an unreachable destination and that test had a balanced count i.e. it was possible to reboot the container.
>
> Do you have an idea why this happens in the ipvs case ?
Hans. I do know that most outstanding references when you clean up a
container get moved to the loopback device. So it may not originally
be the loopback device itself where the reference counting is wrong.
Eric
next prev parent reply other threads:[~2011-04-15 7:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 7:01 unregister_netdevice: waiting for lo to become free. Usage count = 8 Hans Schillstrom
2011-04-15 7:27 ` Eric W. Biederman [this message]
2011-04-15 20:11 ` Julian Anastasov
2011-04-18 6:10 ` Hans Schillstrom
2011-04-18 10:43 ` Hans Schillstrom
2011-04-18 21:12 ` Julian Anastasov
2011-04-18 21:48 ` Hans Schillstrom
2011-04-18 22:23 ` Julian Anastasov
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=m1d3ko9dpj.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=hans@schillstrom.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@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