From: Tariq Toukan <tariqt@nvidia.com>
To: Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
Tariq Toukan <tariqt@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
<netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Gal Pressman <gal@nvidia.com>,
Moshe Shemesh <moshe@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>
Subject: [PATCH net 0/3] mlx5 misc fixes 2026-03-16
Date: Mon, 16 Mar 2026 11:46:00 +0200 [thread overview]
Message-ID: <20260316094603.6999-1-tariqt@nvidia.com> (raw)
Hi,
This patchset provides misc bug fixes from the team to the mlx5
core and Eth drivers.
Thanks,
Tariq.
Cosmin Ratiu (1):
net/mlx5: qos: Restrict RTNL area to avoid a lock cycle
Jianbo Liu (2):
net/mlx5e: Prevent concurrent access to IPSec ASO context
net/mlx5e: Fix race condition during IPSec ESN update
.../mellanox/mlx5/core/en_accel/ipsec.h | 1 +
.../mlx5/core/en_accel/ipsec_offload.c | 50 ++++++++-----------
.../net/ethernet/mellanox/mlx5/core/esw/qos.c | 23 ++++-----
3 files changed, 32 insertions(+), 42 deletions(-)
base-commit: 43d222fbcdff9a715dbe63a0c9e5902f1c9ddd10
--
2.44.0
next reply other threads:[~2026-03-16 9:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 9:46 Tariq Toukan [this message]
2026-03-16 9:46 ` [PATCH net 1/3] net/mlx5: qos: Restrict RTNL area to avoid a lock cycle Tariq Toukan
2026-03-16 9:46 ` [PATCH net 2/3] net/mlx5e: Prevent concurrent access to IPSec ASO context Tariq Toukan
2026-03-16 9:46 ` [PATCH net 3/3] net/mlx5e: Fix race condition during IPSec ESN update Tariq Toukan
2026-03-19 1:00 ` [PATCH net 0/3] mlx5 misc fixes 2026-03-16 patchwork-bot+netdevbpf
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=20260316094603.6999-1-tariqt@nvidia.com \
--to=tariqt@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.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