From: David Miller <davem@davemloft.net>
To: alex@digriz.org.uk
Cc: netdev@vger.kernel.org
Subject: Re: pimreg zombies
Date: Sun, 12 Sep 2010 12:17:13 -0700 (PDT) [thread overview]
Message-ID: <20100912.121713.189706279.davem@davemloft.net> (raw)
In-Reply-To: <2bpal7-l68.ln1@chipmunk.wormnet.eu>
From: Alexander Clouter <alex@digriz.org.uk>
Date: Sat, 4 Sep 2010 22:12:34 +0100
> I am writing a multicast pim daemon and noticed that if I call
> setsockopt(MRT_ADD_VIF), also occurs for IPv6 too, incorrectly on a
> socket established with socket(AF_INET, SOCK_RAW, IPPROTO_PIM)[1] then
> when the application quits I have zombie pimreg (and pimreg6) interfaces
> that can only be disposed of with a reboot.
pimreg interfaces can only be instantiated and removed from userspace
by using the appropriate MRT_*. So you can get rid of these
interfaces by using an appropriate MRT_DEL_VIF call on an IPPROTO_PIM
socket.
They are not automatically removed by the closing of that userland
socket.
prev parent reply other threads:[~2010-09-12 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 21:12 pimreg zombies Alexander Clouter
2010-09-12 19:08 ` David Miller
2010-09-12 19:17 ` David Miller [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=20100912.121713.189706279.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alex@digriz.org.uk \
--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).