linux-kernel - Re: [PATCHv3 net-next 0/2] Exporting IGMP/MLD checking from bridge code

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] [day] [month] [year] [list]

Message-Id: <20150504.144944.1896578946813579544.davem@davemloft.net>
Date:	Mon, 04 May 2015 14:49:44 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	linus.luessing@...3.blue
Cc:	b.a.t.m.a.n@...ts.open-mesh.org, netdev@...r.kernel.org,
	bridge@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
	yoshfuji@...ux-ipv6.org, stephen@...workplumber.org,
	herbert@...dor.apana.org.au, tom@...bertland.com
Subject: Re: [PATCHv3 net-next 0/2] Exporting IGMP/MLD checking from bridge
 code

From: Linus Lüssing <linus.luessing@...3.blue>
Date: Sat,  2 May 2015 14:01:05 +0200

> The multicast optimizations in batman-adv are yet only usable and
> enabled in non-bridged scenarios. To be able to support bridged setups
> batman-adv needs to be able to detect IGMP/MLD queriers and reports on
> mesh nodes without bridges, too. See the following link for details:
> 
> http://www.open-mesh.org/projects/batman-adv/wiki/Multicast-optimizations-listener-reports
> 
> To avoid duplicate code between the bridge and batman-adv, the IGMP/MLD
> message validation code is moved from the bridge to the IPv4/IPv6 stack.
> 
> On the way, some refactoring to increase readability and to iron out
> some subtle differences between the IGMP and MLD parsing code is done.

Series applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/