netdev - Re: PATCH: Add IFF_ALLMULTI support to cpsw (and fix IFF

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]

Date:	Thu, 30 Oct 2014 16:12:52 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	lsorense@...lub.uwaterloo.ca
Cc:	linux-kernel@...r.kernel.org, mugunthanvnm@...com,
	netdev@...r.kernel.org
Subject: Re: PATCH: Add IFF_ALLMULTI support to cpsw (and fix IFF_PROMISC
 support too)

From: "Lennart Sorensen" <lsorense@...lub.uwaterloo.ca>
Date: Wed, 29 Oct 2014 15:06:12 -0400

> The cpsw driver did not support the IFF_ALLMULTI flag which makes dynamic
> multicast routing rather hard to handle.  Related to this, when enabling
> IFF_PROMISC in non dual_emac mode, all registered vlans are flushed,
> and only broadcast and unicast are allowed which isn't what you would
> want from IFF_PROMISC.
> 
> A new cpsw_ale_set_allmulti function now scans through the ALE entry
> table and adds or removes the host port from the unregistered multicast
> port mask depending on the state of IFF_ALLMULTI.  In promisc mode,
> it is also called to enable reception of all multicast traffic.
> 
> With this change I am now able to run dynamic multicast routing and also
> use tcpdump and actually see multicast traffic.
> 
> Signed-off-by: Len Sorensen <lsorense@...lub.uwaterloo.ca>

Please fix your Subject line and resubmit this patch.

Subject lines end up as the commit message header text, and
therefore must be of the form:

subsystem: Description.

In this case "cpsw: " is probably an appropriate subsystem
prefix.
--
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