From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, jiri@nvidia.com,
amcohen@nvidia.com, mlxsw@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net 0/3] mlxsw: Various fixes
Date: Sat, 24 Oct 2020 16:37:30 +0300 [thread overview]
Message-ID: <20201024133733.2107509-1-idosch@idosch.org> (raw)
From: Ido Schimmel <idosch@nvidia.com>
This patch set contains various fixes for mlxsw.
Patch #1 ensures that only link modes that are supported by both the
device and the driver are advertised. When a link mode that is not
supported by the driver is negotiated by the device, it will be
presented as an unknown speed by ethtool, causing the bond driver to
wrongly assume that the link is down.
Patch #2 fixes a trivial memory leak upon module removal.
Patch #3 fixes a use-after-free that syzkaller was able to trigger once
on a slow emulator after a few months of fuzzing.
Amit Cohen (2):
mlxsw: Only advertise link modes supported by both driver and device
mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish()
Ido Schimmel (1):
mlxsw: core: Fix memory leak on module removal
drivers/net/ethernet/mellanox/mlxsw/core.c | 5 ++++
.../net/ethernet/mellanox/mlxsw/spectrum.c | 9 ++++--
.../net/ethernet/mellanox/mlxsw/spectrum.h | 1 +
.../mellanox/mlxsw/spectrum_ethtool.c | 30 +++++++++++++++++++
4 files changed, 43 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-24 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 13:37 Ido Schimmel [this message]
2020-10-24 13:37 ` [PATCH net 1/3] mlxsw: Only advertise link modes supported by both driver and device Ido Schimmel
2020-10-24 13:37 ` [PATCH net 2/3] mlxsw: core: Fix memory leak on module removal Ido Schimmel
2020-10-24 13:37 ` [PATCH net 3/3] mlxsw: core: Fix use-after-free in mlxsw_emad_trans_finish() Ido Schimmel
2020-10-26 23:56 ` [PATCH net 0/3] mlxsw: Various fixes Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2021-02-25 16:57 Ido Schimmel
2021-02-26 23:50 ` patchwork-bot+netdevbpf
2019-09-26 11:43 Ido Schimmel
2019-09-27 18:33 ` 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=20201024133733.2107509-1-idosch@idosch.org \
--to=idosch@idosch.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.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 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.