From: Stephen Hemminger <stephen@networkplumber.org>
To: Davide Caratti <dcaratti@redhat.com>
Cc: Stephen Hemminger <sthemmin@microsoft.com>,
Jiri Pirko <jiri@mellanox.com>,
netdev@vger.kernel.org,
Wolfgang Bumiller <w.bumiller@proxmox.com>,
Michal Privoznik <mprivozn@redhat.com>
Subject: Re: [PATCH iproute2] tc: fix parsing of the control action
Date: Sun, 4 Mar 2018 09:01:54 -0800 [thread overview]
Message-ID: <20180304090154.1b36d04b@xeon-e3> (raw)
In-Reply-To: <59b3a21ecf0c79dcc7cade919ff00f1f0ee73b31.1520015432.git.dcaratti@redhat.com>
On Fri, 2 Mar 2018 19:36:16 +0100
Davide Caratti <dcaratti@redhat.com> wrote:
> If the user didn't specify any control action, don't pop the command line
> arguments: otherwise, parsing of the next argument (tipically the 'index'
> keyword) results in an error, causing the following 'tc-testing' failures:
>
> Test a6d6: Add skbedit action with index
> Test 38f3: Delete skbedit action
> Test a568: Add action with ife type
> Test b983: Add action without ife type
> Test 7d50: Add skbmod action to set destination mac
> Test 9b29: Add skbmod action to set source mac
> Test e93a: Delete an skbmod action
>
> Also, add missing parse for 'ok' control action to m_police, to fix the
> following 'tc-testing' failure:
>
> Test 8dd5: Add police action with control ok
>
> tested with:
> # ./tdc.py
>
> test results:
> all tests ok using kernel 4.16-rc2, except 9aa8 "Get a single skbmod
> action from a list" (which is failing also before this commit)
>
> Fixes: 3572e01a090a ("tc: util: Don't call NEXT_ARG_FWD() in __parse_action_control()")
> Cc: Michal Privoznik <mprivozn@redhat.com>
> Cc: Wolfgang Bumiller <w.bumiller@proxmox.com>
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
> ---
Applied thanks.
prev parent reply other threads:[~2018-03-04 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 18:36 [PATCH iproute2] tc: fix parsing of the control action Davide Caratti
2018-03-04 17:01 ` Stephen Hemminger [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=20180304090154.1b36d04b@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dcaratti@redhat.com \
--cc=jiri@mellanox.com \
--cc=mprivozn@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=w.bumiller@proxmox.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).