All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Waldekranz <tobias@waldekranz.com>
To: Jakub Kicinski <kuba@kernel.org>
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 23:20:18 +0100	[thread overview]
Message-ID: <87tudrbgpp.fsf@waldekranz.com> (raw)
In-Reply-To: <20220125124108.5a19f007@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net>

On Tue, Jan 25, 2022 at 12:41, Jakub Kicinski <kuba@kernel.org> wrote:
> On Tue, 25 Jan 2022 20:05:45 +0100 Tobias Waldekranz wrote:
>> On Tue, Jan 25, 2022 at 10:01, Jakub Kicinski <kuba@kernel.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.

Ahh ok, hope it gets sorted quickly!

>> I guess my question is really: will it still be considered for
>> upcoming stable kernel releases?
>
> Only after the next merge window, but yes.

I had a feeling that would be the case. Aright, not optimal, but not a
big deal either. Thanks for taking the time to respond.

      reply	other threads:[~2022-01-25 22:20 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 ` [PATCH net 0/2] " Jakub Kicinski
2022-01-25 19:05   ` Tobias Waldekranz
2022-01-25 20:41     ` Jakub Kicinski
2022-01-25 22:20       ` Tobias Waldekranz [this message]

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=87tudrbgpp.fsf@waldekranz.com \
    --to=tobias@waldekranz.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    /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.