All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: dsa: Avoid cross-chip syncing of VLAN filtering
Date: Tue, 25 Jan 2022 10:01:31 -0800	[thread overview]
Message-ID: <20220125100131.1e0c7beb@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20220124210944.3749235-1-tobias@waldekranz.com>

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.

  parent reply	other threads:[~2022-01-25 18:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 21:09 [PATCH net 0/2] net: dsa: Avoid cross-chip syncing of VLAN filtering Tobias Waldekranz
2022-01-24 21:09 ` [PATCH net 1/2] net: dsa: Move VLAN filtering syncing out of dsa_switch_bridge_leave Tobias Waldekranz
2022-01-25  0:05   ` Vladimir Oltean
2022-01-24 21:09 ` [PATCH net 2/2] net: dsa: Avoid cross-chip syncing of VLAN filtering Tobias Waldekranz
2022-01-25  0:04   ` Vladimir Oltean
2022-01-25 18:01 ` Jakub Kicinski [this message]
2022-01-25 19:05   ` [PATCH net 0/2] " Tobias Waldekranz
2022-01-25 20:41     ` Jakub Kicinski
2022-01-25 22:20       ` Tobias Waldekranz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220125100131.1e0c7beb@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=tobias@waldekranz.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.