From: Benjamin Thery <benjamin.thery@bull.net>
To: David Miller <davem@davemloft.net>,
Alexey Dobriyan <adobriyan@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] igmp: allow IPPROTO_IGMP sockets in netns
Date: Tue, 16 Dec 2008 16:45:13 +0100 [thread overview]
Message-ID: <4947CD09.6060605@bull.net> (raw)
In-Reply-To: <20080908012919.GD575@x200.localdomain>
Hi,
I was wondering what happened to this patch to support igmp socket
per-netns sent by Alexey in September?
It looks like it has never been merged in net-next-2.6?
There's also this other patch sent at the same time by Alexey to make
igmp proc entries per-netns that was "lost":
http://thread.gmane.org/gmane.linux.network/105226
Thanks,
Benjamin
Alexey Dobriyan wrote:
> Looks like everything is already ready.
>
> Required for ebtables(8) for one thing.
>
> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
> ---
>
> net/ipv4/af_inet.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- a/net/ipv4/af_inet.c
> +++ b/net/ipv4/af_inet.c
> @@ -1310,6 +1310,7 @@ EXPORT_SYMBOL_GPL(snmp_mib_free);
> #ifdef CONFIG_IP_MULTICAST
> static struct net_protocol igmp_protocol = {
> .handler = igmp_rcv,
> + .netns_ok = 1,
> };
> #endif
>
>
> _______________________________________________
> Containers mailing list
> Containers@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
>
>
--
B e n j a m i n T h e r y - BULL/DT/Open Software R&D
http://www.bull.com
next prev parent reply other threads:[~2008-12-16 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 1:29 [PATCH] igmp: allow IPPROTO_IGMP sockets in netns Alexey Dobriyan
2008-12-16 15:45 ` Benjamin Thery [this message]
2008-12-16 23:44 ` David Miller
2008-12-17 8:48 ` Benjamin Thery
-- strict thread matches above, loose matches on Subject: below --
2008-09-08 0:38 Alexey Dobriyan
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=4947CD09.6060605@bull.net \
--to=benjamin.thery@bull.net \
--cc=adobriyan@gmail.com \
--cc=davem@davemloft.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).