From: Jakub Kicinski <kuba@kernel.org>
To: Saeed Mahameed <saeedm@nvidia.com>
Cc: Paul Moore <paul@paul-moore.com>,
Leon Romanovsky <leon@kernel.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
Saeed Mahameed <saeed@kernel.org>, Shay Drory <shayd@nvidia.com>,
netdev@vger.kernel.org, selinux@vger.kernel.org,
Tariq Toukan <tariqt@nvidia.com>
Subject: Re: Potential regression/bug in net/mlx5 driver
Date: Thu, 13 Apr 2023 15:21:50 -0700 [thread overview]
Message-ID: <20230413152150.4b54d6f4@kernel.org> (raw)
In-Reply-To: <ZDhwUYpMFvCRf1EC@x130>
On Thu, 13 Apr 2023 14:12:49 -0700 Saeed Mahameed wrote:
> This is a high priority and we are working on this, unfortunately for mlx5
> we don't check FW versions since we support more than 6 different devices
> already, with different FW production lines.
>
> So we believe that this bug is very hard to solve without breaking backward
> compatibility with the currently supported working FWs, the issue exists only
> on very old firmwares and we will recommend a firmware upgrade to resolve this
> issue.
On a closer read I don't like what this patch is doing at all.
I'm not sure we have precedent for "management connection" functions.
This requires a larger discussion. And after looking up the patch set
it went in, it seems to have been one of the hastily merged ones.
I'm sending a revert.
next prev parent reply other threads:[~2023-04-13 22:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 23:08 Potential regression/bug in net/mlx5 driver Paul Moore
2023-03-29 22:20 ` Saeed Mahameed
2023-03-30 1:27 ` Paul Moore
2023-04-09 8:48 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-09 23:50 ` Paul Moore
2023-04-10 5:46 ` Leon Romanovsky
2023-04-13 13:49 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-13 14:54 ` Jakub Kicinski
2023-04-13 15:19 ` Paul Moore
2023-04-13 21:12 ` Saeed Mahameed
2023-04-13 22:21 ` Jakub Kicinski [this message]
2023-04-13 22:34 ` Saeed Mahameed
2023-04-13 22:51 ` Jakub Kicinski
2023-04-14 3:03 ` Saeed Mahameed
2023-04-14 3:26 ` Jakub Kicinski
2023-04-14 14:37 ` Paul Moore
2023-04-14 22:20 ` Saeed Mahameed
2023-04-15 0:34 ` Jakub Kicinski
2023-04-15 4:40 ` Saeed Mahameed
2023-04-17 15:38 ` Jakub Kicinski
2023-04-20 0:43 ` Saeed Mahameed
2023-04-20 0:46 ` Jakub Kicinski
2023-04-20 4:02 ` Saeed Mahameed
2023-03-31 13:10 ` Linux regression tracking #adding (Thorsten Leemhuis)
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=20230413152150.4b54d6f4@kernel.org \
--to=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=regressions@lists.linux.dev \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.com \
--cc=selinux@vger.kernel.org \
--cc=shayd@nvidia.com \
--cc=tariqt@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 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.