netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mashak <mrv@mojatatu.com>
To: Yuval Mintz <yuvalm@mellanox.com>
Cc: dsahern@gmail.com, mlxsw@mellanox.com, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2-next] tc: Correct json output for actions
Date: Wed, 04 Apr 2018 17:09:04 -0400	[thread overview]
Message-ID: <858ta2brwv.fsf@mojatatu.com> (raw)
In-Reply-To: <1522844653-37136-1-git-send-email-yuvalm@mellanox.com> (Yuval Mintz's message of "Wed, 4 Apr 2018 15:24:13 +0300")

Yuval Mintz <yuvalm@mellanox.com> writes:

> Commit 9fd3f0b255d9 ("tc: enable json output for actions") added JSON
> support for tc-actions at the expense of breaking other use cases that
> reach tc_print_action(), as the latter don't expect the 'actions' array
> to be a new object.
>
> Consider the following taken duringrun of tc_chain.sh selftest,
> and see the latter command output is broken:
>
> $ ./tc/tc -j -p actions list action gact | grep -C 3 actions
> [ {
>         "total acts": 1
>     },{
>         "actions": [ {
>                 "order": 0,
>
> $ ./tc/tc -p -j -s filter show dev enp3s0np2 ingress | grep -C 3 actions
>             },
>             "skip_hw": true,
>             "not_in_hw": true,{
>                 "actions": [ {
>                         "order": 1,
>                         "kind": "gact",
>                         "control_action": {
>
> Relocate the open/close of the JSON object to declare the object only
> for the case that needs it.
>
> Signed-off-by: Yuval Mintz <yuvalm@mellanox.com>

[...]


Good catch, thanks Yuval.

Tested-by: Roman Mashak <mrv@mojatatu.com>

  parent reply	other threads:[~2018-04-04 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04 12:24 [PATCH iproute2-next] tc: Correct json output for actions Yuval Mintz
2018-04-04 17:13 ` David Ahern
2018-04-04 21:09 ` Roman Mashak [this message]
2018-04-04 23:42   ` Stephen Hemminger

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=858ta2brwv.fsf@mojatatu.com \
    --to=mrv@mojatatu.com \
    --cc=dsahern@gmail.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=yuvalm@mellanox.com \
    /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).