netdev - Re: [PATCH net-next] net: dsa: mv88e6xxx: do not flood CPU with unknown multicast

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]

Date:   Wed, 12 Jun 2019 21:56:44 -0400
From:   Vivien Didelot <vivien.didelot@...il.com>
To:     Russell King - ARM Linux admin <linux@...linux.org.uk>
Cc:     netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
        andrew@...n.ch, f.fainelli@...il.com
Subject: Re: [PATCH net-next] net: dsa: mv88e6xxx: do not flood CPU with
 unknown multicast

Hi Russell,

On Thu, 13 Jun 2019 00:25:52 +0100, Russell King - ARM Linux admin <linux@...linux.org.uk> wrote:
> On Wed, Jun 12, 2019 at 06:33:44PM -0400, Vivien Didelot wrote:
> > The DSA ports must flood unknown unicast and multicast, but the switch
> > must not flood the CPU ports with unknown multicast, as this results
> > in a lot of undesirable traffic that the network stack needs to filter
> > in software.
> 
> What if you have configured IPv6 on the bridge device, and are expecting
> the multicasted IPv6 frames for neighbour discovery to work?

Multicast management should still be flooded, so I would expect this
to work? Can you describe the test you want me to run for this case?


Thanks,
Vivien