From: patchwork-bot+netdevbpf@kernel.org
To: Mark Bloch <mbloch@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, sd@queasysnail.net,
kuniyu@amazon.com, leon@kernel.org, dsahern@kernel.org,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
markzhang@nvidia.com, msanalla@nvidia.com
Subject: Re: [PATCH v2 net] rtnetlink: Allocate vfinfo size for VF GUIDs when supported
Date: Thu, 27 Mar 2025 18:50:37 +0000 [thread overview]
Message-ID: <174310143703.2165614.8256610982374403236.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250325090226.749730-1-mbloch@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 25 Mar 2025 11:02:26 +0200 you wrote:
> From: Mark Zhang <markzhang@nvidia.com>
>
> Commit 30aad41721e0 ("net/core: Add support for getting VF GUIDs")
> added support for getting VF port and node GUIDs in netlink ifinfo
> messages, but their size was not taken into consideration in the
> function that allocates the netlink message, causing the following
> warning when a netlink message is filled with many VF port and node
> GUIDs:
> # echo 64 > /sys/bus/pci/devices/0000\:08\:00.0/sriov_numvfs
> # ip link show dev ib0
> RTNETLINK answers: Message too long
> Cannot send link get request: Message too long
>
> [...]
Here is the summary with links:
- [v2,net] rtnetlink: Allocate vfinfo size for VF GUIDs when supported
https://git.kernel.org/netdev/net/c/23f00807619d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-03-27 18:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 9:02 [PATCH v2 net] rtnetlink: Allocate vfinfo size for VF GUIDs when supported Mark Bloch
2025-03-25 15:49 ` Sabrina Dubroca
2025-03-27 18:50 ` patchwork-bot+netdevbpf [this message]
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=174310143703.2165614.8256610982374403236.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=markzhang@nvidia.com \
--cc=mbloch@nvidia.com \
--cc=msanalla@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
/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).