netdev - Re: [PATCH net-next v5 0/2] Multicast group join/leave at ip level

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150227.162611.864498157750734820.davem@davemloft.net>
Date:	Fri, 27 Feb 2015 16:26:11 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	challa@...ronetworks.com
Cc:	eric.dumazet@...il.com, daniel@...earbox.net,
	netdev@...r.kernel.org
Subject: Re: [PATCH net-next v5 0/2] Multicast group join/leave at ip level

From: Madhu Challa <challa@...ronetworks.com>
Date: Wed, 25 Feb 2015 09:58:33 -0800

> This series enables configuring multicast group join/leave at ip level
> by extending the "ip address" command.
> 
> It adds a new control socket mc_autojoin_sock and ifa_flag IFA_F_MCAUTOJOIN
> to invoke the corresponding igmp group join/leave api.
> 
> Since the igmp group join/leave api takes the rtnl_lock the code had to
> be refactored by adding a shim layer prefixed by __ that can be invoked
> by code that already has the rtnl_lock. This way we avoid proliferation of
> work queues.
> 
> The first patch in this series does the refactoring for igmp v6.
> Its based on igmp v4 changes that were added by Eric Dumazet.
> 
> The second patch in this series does the group join/leave based on the
> setting of the IFA_F_MCAUTOJOIN flag.

Applied, but I'm wondering how many hacks we are going to add to the
tree simply because openvswitch does all of it's stuff with non-native
tunneling devices...
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html