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 iproute2-next v2 1/2] iplink: print warning for missing VF data
Date: Wed, 27 Jan 2021 20:51:56 -0700 [thread overview]
Message-ID: <4e6dac6d-7b2a-ada4-6168-87a1b5f36a0c@gmail.com> (raw)
In-Reply-To: <20210126174054.185084-1-edwin.peer@broadcom.com>
On 1/26/21 10:40 AM, Edwin Peer wrote:
> The kernel might truncate VF info in IFLA_VFINFO_LIST. Compare the
> expected number of VFs in IFLA_NUM_VF to how many were found in the
> list and warn accordingly.
>
> Signed-off-by: Edwin Peer <edwin.peer@broadcom.com>
> ---
> ip/ipaddress.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/ip/ipaddress.c b/ip/ipaddress.c
> index 571346b15cc3..0bbcee2b3bb2 100644
> --- a/ip/ipaddress.c
> +++ b/ip/ipaddress.c
> @@ -922,6 +922,7 @@ int print_linkinfo(struct nlmsghdr *n, void *arg)
> const char *name;
> unsigned int m_flag = 0;
> SPRINT_BUF(b1);
> + bool truncated_vfs = false;
>
> if (n->nlmsg_type != RTM_NEWLINK && n->nlmsg_type != RTM_DELLINK)
> return 0;
> @@ -1199,15 +1200,18 @@ int print_linkinfo(struct nlmsghdr *n, void *arg)
>
> if ((do_link || show_details) && tb[IFLA_VFINFO_LIST] && tb[IFLA_NUM_VF]) {
> struct rtattr *i, *vflist = tb[IFLA_VFINFO_LIST];
> - int rem = RTA_PAYLOAD(vflist);
> + int rem = RTA_PAYLOAD(vflist), count = 0;
>
> open_json_array(PRINT_JSON, "vfinfo_list");
> for (i = RTA_DATA(vflist); RTA_OK(i, rem); i = RTA_NEXT(i, rem)) {
> open_json_object(NULL);
> print_vfinfo(fp, ifi, i);
> close_json_object();
> + count++;
> }
> close_json_array(PRINT_JSON, NULL);
> + if (count != rta_getattr_u32(tb[IFLA_NUM_VF]))
> + truncated_vfs = true;
> }
>
> if (tb[IFLA_PROP_LIST]) {
> @@ -1228,6 +1232,9 @@ int print_linkinfo(struct nlmsghdr *n, void *arg)
>
> print_string(PRINT_FP, NULL, "%s", "\n");
> fflush(fp);
> + /* prettier here if stderr and stdout go to the same place */
> + if (truncated_vfs)
> + fprintf(stderr, "Truncated VF list: %s\n", name);
> return 1;
> }
>
>
LGTM. I think it should go to the main branch versus -next.
prev parent reply other threads:[~2021-01-28 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 17:40 [PATCH iproute2-next v2 1/2] iplink: print warning for missing VF data Edwin Peer
2021-01-26 17:40 ` [PATCH iproute2-next v2 2/2] iplink: filter stats using RTEXT_FILTER_SKIP_STATS Edwin Peer
2021-01-28 3:51 ` 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=4e6dac6d-7b2a-ada4-6168-87a1b5f36a0c@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).