From: Ido Schimmel <idosch@idosch.org>
To: David Miller <davem@davemloft.net>
Cc: jiri@resnulli.us, netdev@vger.kernel.org, eladr@mellanox.com,
idosch@mellanox.com, yotamg@mellanox.com, nogahf@mellanox.com,
ogerlitz@mellanox.com
Subject: Re: [patch net] mlxsw: spectrum: Fix incorrect reuse of MID entries
Date: Mon, 31 Oct 2016 22:36:16 +0200 [thread overview]
Message-ID: <20161031203616.3yuvu2l4k3xf6yb7@splinter> (raw)
In-Reply-To: <20161031.153606.989406936490082438.davem@davemloft.net>
Hi,
On Mon, Oct 31, 2016 at 03:36:06PM -0400, David Miller wrote:
> From: Jiri Pirko <jiri@resnulli.us>
> Date: Sun, 30 Oct 2016 10:09:22 +0100
>
> > From: Ido Schimmel <idosch@mellanox.com>
> >
> > In the device, a MID entry represents a group of local ports, which can
> > later be bound to a MDB entry.
> >
> > The lookup of an existing MID entry is currently done using the provided
> > MC MAC address and VID, from the Linux bridge. However, this can result
> > in an incorrect reuse of the same MID index in different VLAN-unaware
> > bridges (same IP MC group and VID 0).
> >
> > Fix this by performing the lookup based on FID instead of VID, which is
> > unique across different bridges.
> >
> > Fixes: 3a49b4fde2a1 ("mlxsw: Adding layer 2 multicast support")
> > Signed-off-by: Ido Schimmel <idosch@mellanox.com>
> > Acked-by: Elad Raz <eladr@mellanox.com>
> > Signed-off-by: Jiri Pirko <jiri@mellanox.com>
>
> Applied, should I queue this up for -stable?
I don't think it's necessary, but thanks for asking! We recently picked
up the habit of noting what we would like to see in -stable.
prev parent reply other threads:[~2016-10-31 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 9:09 [patch net] mlxsw: spectrum: Fix incorrect reuse of MID entries Jiri Pirko
2016-10-31 19:36 ` David Miller
2016-10-31 20:36 ` Ido Schimmel [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=20161031203616.3yuvu2l4k3xf6yb7@splinter \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=idosch@mellanox.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=nogahf@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=yotamg@mellanox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).