From: Paul Moore <paul@paul-moore.com>
To: Shay Drory <shayd@nvidia.com>, Saeed Mahameed <saeedm@nvidia.com>
Cc: netdev@vger.kernel.org, regressions@lists.linux.dev,
selinux@vger.kernel.org
Subject: Potential regression/bug in net/mlx5 driver
Date: Tue, 28 Mar 2023 19:08:34 -0400 [thread overview]
Message-ID: <CAHC9VhQ7A4+msL38WpbOMYjAqLp0EtOjeLh4Dc6SQtD6OUvCQg@mail.gmail.com> (raw)
Hello all,
Starting with the v6.3-rcX kernel releases I noticed that my
InfiniBand devices were no longer present under /sys/class/infiniband,
causing some of my automated testing to fail. It took me a while to
find the time to bisect the issue, but I eventually identified the
problematic commit:
commit fe998a3c77b9f989a30a2a01fb00d3729a6d53a4
Author: Shay Drory <shayd@nvidia.com>
Date: Wed Jun 29 11:38:21 2022 +0300
net/mlx5: Enable management PF initialization
Enable initialization of DPU Management PF, which is a new loopback PF
designed for communication with BMC.
For now Management PF doesn't support nor require most upper layer
protocols so avoid them.
Signed-off-by: Shay Drory <shayd@nvidia.com>
Reviewed-by: Eran Ben Elisha <eranbe@nvidia.com>
Reviewed-by: Moshe Shemesh <moshe@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
I'm not a mlx5 driver expert so I can't really offer much in the way
of a fix, but as a quick test I did remove the
'mlx5_core_is_management_pf(...)' calls in mlx5/core/dev.c and
everything seemed to work okay on my test system (or rather the tests
ran without problem).
If you need any additional information, or would like me to test a
patch, please let me know.
--
paul-moore.com
next reply other threads:[~2023-03-28 23:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-28 23:08 Paul Moore [this message]
2023-03-29 22:20 ` Potential regression/bug in net/mlx5 driver 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
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=CAHC9VhQ7A4+msL38WpbOMYjAqLp0EtOjeLh4Dc6SQtD6OUvCQg@mail.gmail.com \
--to=paul@paul-moore.com \
--cc=netdev@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=saeedm@nvidia.com \
--cc=selinux@vger.kernel.org \
--cc=shayd@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;
as well as URLs for NNTP newsgroup(s).