netdev - Re: [PATCH stable 0/4] net: mscc: ocelot: allow unregistered IP multicast flooding

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: <Yr2jqJumiLlwJXew@kroah.com>
Date:   Thu, 30 Jun 2022 15:22:48 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Vladimir Oltean <vladimir.oltean@....com>
Cc:     stable <stable@...r.kernel.org>, Sasha Levin <sashal@...nel.org>,
        netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Xiaoliang Yang <xiaoliang.yang_1@....com>,
        Claudiu Manoil <claudiu.manoil@....com>,
        Alexandre Belloni <alexandre.belloni@...tlin.com>,
        UNGLinuxDriver@...rochip.com, Andrew Lunn <andrew@...n.ch>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Florian Fainelli <f.fainelli@...il.com>,
        Maxim Kochetkov <fido_max@...ox.ru>,
        Colin Foster <colin.foster@...advantage.com>
Subject: Re: [PATCH stable 0/4] net: mscc: ocelot: allow unregistered IP
 multicast flooding

On Tue, Jun 28, 2022 at 08:20:12PM +0300, Vladimir Oltean wrote:
> This series contains 4 patches (1 for each stable branch: 4.19, 5.4, 5.10 and 5.15)
> which fix 2 variations of the same problem:
> 
> - Between kernels 4.18 and 5.12, IP multicast flooding on ocelot ports
>   is completely broken, both for autonomous forwarding and for local CPU
>   termination. The patches for 4.19 and for 5.10 fix this.
> 
> - Between kernels 5.12 and 5.18, the flooding problem has been fixed for
>   autonomously forwarded IP multicast flows via a new feature commit
>   which cannot be backported, but still remains broken for local CPU
>   termination. The patch for 5.15 fixes this.
> 
> After kernel 5.18, the CPU flooding problem has also been fixed via a
> new feature commit which also cannot be backported. So in the current
> "net" tree, both kinds of IP multicast flooding work properly, and this
> is the reason why these patches target just the "stable" trees.

All now queued up, thanks.

greg k-h