From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, jiri@mellanox.com, mlxsw@mellanox.com,
Ido Schimmel <idosch@mellanox.com>
Subject: [PATCH net 0/2] mlxsw: Couple of fixes
Date: Sun, 29 Dec 2019 13:40:21 +0200 [thread overview]
Message-ID: <20191229114023.60873-1-idosch@idosch.org> (raw)
From: Ido Schimmel <idosch@mellanox.com>
This patch set contains two fixes for mlxsw. Please consider both for
stable.
Patch #1 from Amit fixes a wrong check during MAC validation when
creating router interfaces (RIFs). Given a particular order of
configuration this can result in the driver refusing to create new RIFs.
Patch #2 fixes a wrong trap configuration in which VRRP packets and
routing exceptions were policed by the same policer towards the CPU. In
certain situations this can prevent VRRP packets from reaching the CPU.
Amit Cohen (1):
mlxsw: spectrum_router: Skip loopback RIFs during MAC validation
Ido Schimmel (1):
mlxsw: spectrum: Use dedicated policer for VRRP packets
drivers/net/ethernet/mellanox/mlxsw/reg.h | 1 +
drivers/net/ethernet/mellanox/mlxsw/spectrum.c | 9 +++++++--
drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c | 3 +++
3 files changed, 11 insertions(+), 2 deletions(-)
--
2.24.1
next reply other threads:[~2019-12-29 11:41 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 11:40 Ido Schimmel [this message]
2019-12-29 11:40 ` [PATCH net 1/2] mlxsw: spectrum_router: Skip loopback RIFs during MAC validation Ido Schimmel
2019-12-29 11:40 ` [PATCH net 2/2] mlxsw: spectrum: Use dedicated policer for VRRP packets Ido Schimmel
2019-12-29 20:30 ` [PATCH net 0/2] mlxsw: Couple of fixes David Miller
-- strict thread matches above, loose matches on Subject: below --
2020-11-17 17:33 Ido Schimmel
2020-11-18 19:09 ` Jakub Kicinski
2018-10-29 14:26 Ido Schimmel
2018-10-30 3:48 ` David Miller
2018-10-04 15:48 Ido Schimmel
2018-10-04 16:56 ` David Miller
2018-10-04 17:05 ` Ido Schimmel
2018-02-27 11:56 [patch net 0/2] mlxsw: couple " Jiri Pirko
2018-02-27 19:39 ` David Miller
2018-02-28 7:09 ` Jiri Pirko
2018-01-10 10:42 Jiri Pirko
2018-01-10 20:58 ` David Miller
2017-08-04 12:12 [patch net 0/2] mlxsw: Couple " Jiri Pirko
2017-08-04 18:17 ` David Miller
2017-05-18 7:18 [patch net 0/2] mlxsw: couple " Jiri Pirko
2017-05-18 15:05 ` David Miller
2017-03-14 12:59 [patch net 0/2] mlxsw: Couple " Jiri Pirko
2017-03-14 18:35 ` David Miller
2016-11-11 10:20 Jiri Pirko
2016-11-13 17:48 ` David Miller
2016-10-25 9:25 Jiri Pirko
2016-10-28 17:44 ` David Miller
2016-10-04 7:46 Jiri Pirko
2016-10-05 0:29 ` David Miller
2016-10-05 11:14 ` Jiri Pirko
2016-09-08 6:16 [patch net 0/2] mlxsw: couple " Jiri Pirko
2016-09-09 23:57 ` David Miller
2016-08-24 9:18 Jiri Pirko
2016-08-24 16:39 ` David Miller
2016-06-17 13:09 Jiri Pirko
2016-06-18 4:58 ` David Miller
2016-06-09 7:51 Jiri Pirko
2016-06-09 18:21 ` David Miller
2016-05-06 20:18 [patch net 0/2] mlxsw: Couple " Jiri Pirko
2016-05-06 22:33 ` David Miller
2016-03-07 8:24 [patch net 0/2] mlxsw: couple " Jiri Pirko
2015-10-08 13:17 Jiri Pirko
2015-10-11 12:08 ` David Miller
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=20191229114023.60873-1-idosch@idosch.org \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--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 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).