From: David Ahern <dsahern@gmail.com>
To: Edwin Peer <edwin.peer@broadcom.com>, netdev@vger.kernel.org
Cc: Jakub Kicinski <kuba@kernel.org>,
Andrew Gospodarek <andrew.gospodarek@broadcom.com>,
Michael Chan <michael.chan@broadcom.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Michal Kubecek <mkubecek@suse.cz>
Subject: Re: [PATCH net-next v2 1/1] rtnetlink: extend RTEXT_FILTER_SKIP_STATS to IFLA_VF_INFO
Date: Wed, 27 Jan 2021 20:50:07 -0700 [thread overview]
Message-ID: <7427e82d-e19d-bfe6-03d1-7fdab3dfe26a@gmail.com> (raw)
In-Reply-To: <20210126174024.185001-2-edwin.peer@broadcom.com>
On 1/26/21 10:40 AM, Edwin Peer wrote:
> This filter already exists for excluding IPv6 SNMP stats. Extend its
> definition to also exclude IFLA_VF_INFO stats in RTM_GETLINK.
>
> This patch constitutes a partial fix for a netlink attribute nesting
> overflow bug in IFLA_VFINFO_LIST. By excluding the stats when the
> requester doesn't need them, the truncation of the VF list is avoided.
>
> While it was technically only the stats added in commit c5a9f6f0ab40
> ("net/core: Add drop counters to VF statistics") breaking the camel's
> back, the appreciable size of the stats data should never have been
> included without due consideration for the maximum number of VFs
> supported by PCI.
>
> Fixes: 3b766cd83232 ("net/core: Add reading VF statistics through the PF netdevice")
> Fixes: c5a9f6f0ab40 ("net/core: Add drop counters to VF statistics")
> Signed-off-by: Edwin Peer <edwin.peer@broadcom.com>
> ---
> net/core/rtnetlink.c | 96 +++++++++++++++++++++++---------------------
> 1 file changed, 51 insertions(+), 45 deletions(-)
>
looks reasonable to me - userspace is opting out of data it does not want.
prev parent reply other threads:[~2021-01-28 4:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 17:40 [PATCH net-next v2 0/1] support more VFs in RTM_GETLINK Edwin Peer
2021-01-26 17:40 ` [PATCH net-next v2 1/1] rtnetlink: extend RTEXT_FILTER_SKIP_STATS to IFLA_VF_INFO Edwin Peer
2021-01-26 20:36 ` Jakub Kicinski
2021-01-26 22:42 ` Edwin Peer
2021-01-28 3:50 ` David Ahern [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=7427e82d-e19d-bfe6-03d1-7fdab3dfe26a@gmail.com \
--to=dsahern@gmail.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=edwin.peer@broadcom.com \
--cc=kuba@kernel.org \
--cc=michael.chan@broadcom.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).