netdev - Re: [PATCH net 0/2] net: dsa: Avoid cross-chip syncing of VLAN filtering

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: <20220125124108.5a19f007@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>
Date:   Tue, 25 Jan 2022 12:41:08 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Tobias Waldekranz <tobias@...dekranz.com>
Cc:     davem@...emloft.net, netdev@...r.kernel.org
Subject: Re: [PATCH net 0/2] net: dsa: Avoid cross-chip syncing of VLAN
 filtering

On Tue, 25 Jan 2022 20:05:45 +0100 Tobias Waldekranz wrote:
> On Tue, Jan 25, 2022 at 10:01, Jakub Kicinski <kuba@...nel.org> wrote:
> > On Mon, 24 Jan 2022 22:09:42 +0100 Tobias Waldekranz wrote:  
> >> This bug has been latent in the source for quite some time, I suspect
> >> due to the homogeneity of both typical configurations and hardware.
> >> 
> >> On singlechip systems, this would never be triggered. The only reason
> >> I saw it on my multichip system was because not all chips had the same
> >> number of ports, which means that the misdemeanor alien call turned
> >> into a felony array-out-of-bounds access.  
> >
> > Applied, thanks, 934d0f039959 ("Merge branch
> > 'dsa-avoid-cross-chip-vlan-sync'") in net-next.  
> 
> Is there a particular reason that this was applied to net-next?

Not sure, there were issues with kernel.org infra during the night,
could be unintentional.

> I guess my question is really: will it still be considered for
> upcoming stable kernel releases?

Only after the next merge window, but yes.