From: Serhey Popovych <serhe.popovych@gmail.com>
To: David Ahern <dsahern@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next v2 1/6] ipaddress: Improve print_linkinfo()
Date: Thu, 1 Feb 2018 12:59:17 +0200 [thread overview]
Message-ID: <aa8ced71-2449-4342-7eb3-099574d91bb0@gmail.com> (raw)
In-Reply-To: <29ec7a5e-ba5e-4d23-5bb4-7f8e0f422916@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3795 bytes --]
David Ahern wrote:
> On 1/30/18 11:09 AM, Serhey Popovych wrote:
>
>> diff --git a/ip/ipaddress.c b/ip/ipaddress.c
>> index 051a05f..f8fd392 100644
>> --- a/ip/ipaddress.c
>> +++ b/ip/ipaddress.c
>> @@ -948,14 +948,14 @@ int print_linkinfo_brief(const struct sockaddr_nl *who,
>> parse_rtattr(tb, IFLA_MAX, IFLA_RTA(ifi), len);
>> if (tb[IFLA_IFNAME] == NULL) {
>> fprintf(stderr, "BUG: device with ifindex %d has nil ifname\n", ifi->ifi_index);
>> - name = "<nil>";
>> + name = ll_index_to_name(ifi->ifi_index);
>
> This is one of those "should never happen checks" since the kernel
> always adds IFLA_IFNAME. Going to a cache to get a name for the index
> when the existing message is missing that attribute seems wrong. I
> realize the expectation is that the cache is empty today so if%d is
> returned, but that could change and it is the idea of consulting a cache
> that I think is wrong.
>
> If that intention is to have a name I think it is safer to just have it
> set to if%d here (or in a helper that the cache also uses).
In my opinion in print_*() functions it is expected that cache isn't
empty. That's actually point where we benefit from cache.
I understand side effects this change may introduce and your concerns
about them. Will present small set of changes to export "if%d" template
from lib/ll_map.c for use here.
Using "<nil>" of something other, even for "should never happen" case
seems wrong to me.
>
>> } else {
>> name = rta_getattr_str(tb[IFLA_IFNAME]);
>> }
>>
>> if (pfilter->label &&
>> (!pfilter->family || pfilter->family == AF_PACKET) &&
>> - fnmatch(pfilter->label, RTA_DATA(tb[IFLA_IFNAME]), 0))
>> + fnmatch(pfilter->label, name, 0))
>> return -1;
>>
>> if (tb[IFLA_GROUP]) {
>> @@ -1057,6 +1057,7 @@ int print_linkinfo(const struct sockaddr_nl *who,
>> struct ifinfomsg *ifi = NLMSG_DATA(n);
>> struct rtattr *tb[IFLA_MAX+1];
>> int len = n->nlmsg_len;
>> + const char *name;
>> unsigned int m_flag = 0;
>>
>> if (n->nlmsg_type != RTM_NEWLINK && n->nlmsg_type != RTM_DELLINK)
>> @@ -1067,18 +1068,22 @@ int print_linkinfo(const struct sockaddr_nl *who,
>> return -1;
>>
>> if (filter.ifindex && ifi->ifi_index != filter.ifindex)
>> - return 0;
>> + return -1;
>> if (filter.up && !(ifi->ifi_flags&IFF_UP))
>> - return 0;
>> + return -1;
>>
>> parse_rtattr(tb, IFLA_MAX, IFLA_RTA(ifi), len);
>> - if (tb[IFLA_IFNAME] == NULL)
>> + if (tb[IFLA_IFNAME] == NULL) {
>> fprintf(stderr, "BUG: device with ifindex %d has nil ifname\n", ifi->ifi_index);
>> + name = ll_index_to_name(ifi->ifi_index);
>
> same here
>
>
>> + } else {
>> + name = rta_getattr_str(tb[IFLA_IFNAME]);
>> + }
>>
>> if (filter.label &&
>> (!filter.family || filter.family == AF_PACKET) &&
>> - fnmatch(filter.label, RTA_DATA(tb[IFLA_IFNAME]), 0))
>> - return 0;
>> + fnmatch(filter.label, name, 0))
>> + return -1;
>>
>> if (tb[IFLA_GROUP]) {
>> int group = rta_getattr_u32(tb[IFLA_GROUP]);
>> @@ -1105,16 +1110,7 @@ int print_linkinfo(const struct sockaddr_nl *who,
>> print_bool(PRINT_ANY, "deleted", "Deleted ", true);
>>
>> print_int(PRINT_ANY, "ifindex", "%d: ", ifi->ifi_index);
>> - if (tb[IFLA_IFNAME]) {
>> - print_color_string(PRINT_ANY,
>> - COLOR_IFNAME,
>> - "ifname", "%s",
>> - rta_getattr_str(tb[IFLA_IFNAME]));
>> - } else {
>> - print_null(PRINT_JSON, "ifname", NULL, NULL);
>> - print_color_null(PRINT_FP, COLOR_IFNAME,
>> - "ifname", "%s", "<nil>");
>> - }
>> + print_color_string(PRINT_ANY, COLOR_IFNAME, "ifname", "%s", name);
>>
>> if (tb[IFLA_LINK]) {
>> int iflink = rta_getattr_u32(tb[IFLA_LINK]);
>>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2018-02-01 10:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 18:09 [PATCH iproute2-next v2 0/6] ipaddress: Get rid of print_linkinfo_brief() Serhey Popovych
2018-01-30 18:09 ` [PATCH iproute2-next v2 1/6] ipaddress: Improve print_linkinfo() Serhey Popovych
2018-02-01 3:29 ` David Ahern
2018-02-01 10:59 ` Serhey Popovych [this message]
2018-01-30 18:09 ` [PATCH iproute2-next v2 2/6] ipaddress: Simplify print_linkinfo_brief() and it's usage Serhey Popovych
2018-02-01 3:43 ` David Ahern
2018-02-01 11:00 ` Serhey Popovych
2018-01-30 18:09 ` [PATCH iproute2-next v2 3/6] lib: Correct object file dependencies Serhey Popovych
2018-01-30 18:09 ` [PATCH iproute2-next v2 4/6] utils: Introduce and use get_ifname_rta() Serhey Popovych
2018-02-01 3:45 ` David Ahern
2018-01-30 18:09 ` [PATCH iproute2-next v2 5/6] utils: Introduce and use print_name_and_link() to print name@link Serhey Popovych
2018-02-01 3:50 ` David Ahern
2018-02-01 11:09 ` Serhey Popovych
2018-02-01 15:40 ` David Ahern
2018-01-30 18:09 ` [PATCH iproute2-next v2 6/6] ipaddress: Make print_linkinfo_brief() static Serhey Popovych
2018-02-01 3:53 ` [PATCH iproute2-next v2 0/6] ipaddress: Get rid of print_linkinfo_brief() David Ahern
2018-02-01 11:12 ` Serhey Popovych
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=aa8ced71-2449-4342-7eb3-099574d91bb0@gmail.com \
--to=serhe.popovych@gmail.com \
--cc=dsahern@gmail.com \
--cc=netdev@vger.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).