From: Jianbo Liu <jianbol@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>, Tariq Toukan <tariqt@nvidia.com>
Cc: Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Saeed Mahameed <saeedm@nvidia.com>,
Leon Romanovsky <leon@kernel.org>,
"Mark Bloch" <mbloch@nvidia.com>, <netdev@vger.kernel.org>,
<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Gal Pressman <gal@nvidia.com>
Subject: Re: [PATCH net V2 2/3] net/mlx5e: Prevent entering switchdev mode with inconsistent netns
Date: Wed, 17 Sep 2025 15:07:24 +0800 [thread overview]
Message-ID: <a720eef5-a01c-4449-8ea0-7cd0d05df25b@nvidia.com> (raw)
In-Reply-To: <20250916172106.593683a8@kernel.org>
On 9/17/2025 8:21 AM, Jakub Kicinski wrote:
> On Mon, 15 Sep 2025 15:24:33 +0300 Tariq Toukan wrote:
>> If the PF's netns has been moved and differs from the devlink's netns,
>> enabling switchdev mode would create a state where the OVS control
>> plane (ovs-vsctl) cannot manage the switch because the PF uplink
>> representor and the other representors are split across different
>> namespaces.
>
> I appreciate the extra paragraph of explanation but it's still not
> a fix.
Ack.
next prev parent reply other threads:[~2025-09-17 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 12:24 [PATCH net V2 0/3] mlx5e misc fixes 2025-09-15 Tariq Toukan
2025-09-15 12:24 ` [PATCH net V2 1/3] net/mlx5e: Harden uplink netdev access against device unbind Tariq Toukan
2025-09-15 12:24 ` [PATCH net V2 2/3] net/mlx5e: Prevent entering switchdev mode with inconsistent netns Tariq Toukan
2025-09-17 0:21 ` Jakub Kicinski
2025-09-17 7:07 ` Jianbo Liu [this message]
2025-09-15 12:24 ` [PATCH net V2 3/3] net/mlx5e: Add a miss level for ipsec crypto offload Tariq Toukan
2025-09-17 0:30 ` [PATCH net V2 0/3] mlx5e misc fixes 2025-09-15 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=a720eef5-a01c-4449-8ea0-7cd0d05df25b@nvidia.com \
--to=jianbol@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--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=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@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 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).