From: Simon Horman <horms@kernel.org>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: linux-hyperv@vger.kernel.org, netdev@vger.kernel.org,
decui@microsoft.com, stephen@networkplumber.org,
kys@microsoft.com, paulros@microsoft.com, olaf@aepfle.de,
vkuznets@redhat.com, davem@davemloft.net, wei.liu@kernel.org,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
leon@kernel.org, longli@microsoft.com,
ssengar@linux.microsoft.com, linux-rdma@vger.kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com,
bpf@vger.kernel.org, ast@kernel.org, hawk@kernel.org,
tglx@linutronix.de, shradhagupta@linux.microsoft.com,
andrew+netdev@lunn.ch, kotaranov@microsoft.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next,v2] net: mana: Add support for Multi Vports on Bare metal
Date: Wed, 21 May 2025 15:02:31 +0100 [thread overview]
Message-ID: <20250521140231.GW365796@horms.kernel.org> (raw)
In-Reply-To: <1747671636-5810-1-git-send-email-haiyangz@microsoft.com>
On Mon, May 19, 2025 at 09:20:36AM -0700, Haiyang Zhang wrote:
> To support Multi Vports on Bare metal, increase the device config response
> version. And, skip the register HW vport, and register filter steps, when
> the Bare metal hostmode is set.
>
> Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
> ---
> v2:
> Updated comments as suggested by ALOK TIWARI.
> Fixed the version check.
>
> ---
> drivers/net/ethernet/microsoft/mana/mana_en.c | 24 ++++++++++++-------
> include/net/mana/mana.h | 4 +++-
> 2 files changed, 19 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/net/ethernet/microsoft/mana/mana_en.c b/drivers/net/ethernet/microsoft/mana/mana_en.c
> index 2bac6be8f6a0..9c58d9e0bbb5 100644
> --- a/drivers/net/ethernet/microsoft/mana/mana_en.c
> +++ b/drivers/net/ethernet/microsoft/mana/mana_en.c
> @@ -921,7 +921,7 @@ static void mana_pf_deregister_filter(struct mana_port_context *apc)
>
> static int mana_query_device_cfg(struct mana_context *ac, u32 proto_major_ver,
> u32 proto_minor_ver, u32 proto_micro_ver,
> - u16 *max_num_vports)
> + u16 *max_num_vports, u8 *bm_hostmode)
> {
> struct gdma_context *gc = ac->gdma_dev->gdma_context;
> struct mana_query_device_cfg_resp resp = {};
> @@ -932,7 +932,7 @@ static int mana_query_device_cfg(struct mana_context *ac, u32 proto_major_ver,
> mana_gd_init_req_hdr(&req.hdr, MANA_QUERY_DEV_CONFIG,
> sizeof(req), sizeof(resp));
>
> - req.hdr.resp.msg_version = GDMA_MESSAGE_V2;
> + req.hdr.resp.msg_version = GDMA_MESSAGE_V3;
>
> req.proto_major_ver = proto_major_ver;
> req.proto_minor_ver = proto_minor_ver;
> @@ -956,11 +956,16 @@ static int mana_query_device_cfg(struct mana_context *ac, u32 proto_major_ver,
>
> *max_num_vports = resp.max_num_vports;
>
> - if (resp.hdr.response.msg_version == GDMA_MESSAGE_V2)
> + if (resp.hdr.response.msg_version >= GDMA_MESSAGE_V2)
> gc->adapter_mtu = resp.adapter_mtu;
> else
> gc->adapter_mtu = ETH_FRAME_LEN;
>
> + if (resp.hdr.response.msg_version >= GDMA_MESSAGE_V3)
> + *bm_hostmode = resp.bm_hostmode;
> + else
> + *bm_hostmode = 0;
Hi,
Perhaps not strictly related to this patch, but I see
that mana_verify_resp_hdr() is called a few lines above.
And that verifies a minimum msg_version. But I do not see
any verification of the maximum msg_version supported by the code.
I am concerned about a hypothetical scenario where, say the as yet unknown
version 5 is sent as the version, and the above behaviour is used, while
not being correct.
Could you shed some light on this?
...
next prev parent reply other threads:[~2025-05-21 14:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 16:20 [PATCH net-next,v2] net: mana: Add support for Multi Vports on Bare metal Haiyang Zhang
2025-05-21 14:02 ` Simon Horman [this message]
2025-05-21 17:28 ` [EXTERNAL] " Haiyang Zhang
2025-05-22 12:02 ` Simon Horman
2025-05-22 13:43 ` Paolo Abeni
2025-05-22 14:51 ` Haiyang Zhang
2025-05-28 6:27 ` Paolo Abeni
2025-05-28 6:40 ` 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=20250521140231.GW365796@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=haiyangz@microsoft.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=pabeni@redhat.com \
--cc=paulros@microsoft.com \
--cc=shradhagupta@linux.microsoft.com \
--cc=ssengar@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wei.liu@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 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).