From: Vladis Dronov <vdronov@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, David Ahern <dsahern@gmail.com>,
George Shuklin <george.shuklin@gmail.com>
Subject: Re: [PATCH iproute2] ip: fix link type and vlan oneline output
Date: Tue, 21 Jan 2020 11:59:14 -0500 (EST) [thread overview]
Message-ID: <1671392030.4223005.1579625954850.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20200120093404.172208c2@hermes.lan>
hello,
> The change to ipaddress.c was incorrect. You can't change the order of things
> in the output.
i still believe it is bad to break a single link layers options line with
a multi-line piece:
5: veth90.4000@veth90: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 26:9a:05:af:db:00 brd ff:ff:ff:ff:ff:ff promiscuity 0 minmtu 0 maxmtu 65535
vlan protocol 802.1Q id 4000 <REORDER_HDR> the option line is broken ^^^ by \n in print_linktype()
ingress-qos-map { 1:2 }
egress-qos-map { 2:1 } addrgenmode eui64 numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
^^^ the option line continues here
print_linktype() has an unconditional \n so it always breaks a link layer
options line. this output is assumed to be human-readable, so i believe,
proper indentation is more important that an order of fields. a machine-
readable format is another one, as far as i understand.
i'm not sure how "an order of things" is supposed to be stable, if
print_linktype() outputs a variable number of variable fields (depending
on a link type) in the middle of a link layer options.
surely, if an order of things in this understanding is above all, please,
ignore my rant.
also, with the change a commit message should be different. i understand,
it is too late to change it, but still. let a proper message be at least
here, in the mail thread:
>>> begin >>>
Add oneline support for vlan's ingress and egress qos maps.
Before the fix:
# ip -oneline -details link show veth90.4000
5: veth90.4000@veth90: ... maxmtu 65535 \ vlan protocol 802.1Q id 4000 <REORDER_HDR>
ingress-qos-map { 1:2 } <<< a multiline output despite -oneline
egress-qos-map { 2:1 } addrgenmode eui64 numtxqueues 1 ...
After the fix:
# ip -details link show veth90.4000
5: veth90.4000@veth90: ... maxmtu 65535 \ vlan protocol 802.1Q id 4000 <REORDER_HDR> \ ingress-qos-map { 1:2 } \ egress-qos-map { 2:1 } addrgenmode eui64 numtxqueues 1 ...
<<< end <<<
> Second, you needed to have a Fixes tag. In this case, it went back to
> original vlan support.
indeed, this is my mistake, thank you for correcting this in the patch
submitted.
Best regards,
Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer
----- Original Message -----
> From: "Stephen Hemminger" <stephen@networkplumber.org>
> To: "Vladis Dronov" <vdronov@redhat.com>
> Cc: netdev@vger.kernel.org, "David Ahern" <dsahern@gmail.com>, "George Shuklin" <george.shuklin@gmail.com>
> Sent: Monday, January 20, 2020 6:34:04 PM
> Subject: Re: [PATCH iproute2] ip: fix link type and vlan oneline output
>
> The change to ipaddress.c was incorrect. You can't change the order of things
> in the output.
>
> Second, you needed to have a Fixes tag. In this case, it went back to
> original vlan support.
prev parent reply other threads:[~2020-01-21 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-19 1:12 [PATCH iproute2] ip: fix link type and vlan oneline output Vladis Dronov
2020-01-19 1:28 ` Vladis Dronov
2020-01-20 17:34 ` Stephen Hemminger
2020-01-21 16:59 ` Vladis Dronov [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=1671392030.4223005.1579625954850.JavaMail.zimbra@redhat.com \
--to=vdronov@redhat.com \
--cc=dsahern@gmail.com \
--cc=george.shuklin@gmail.com \
--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).