From: Stephen Hemminger <stephen@networkplumber.org>
To: Vlad Buslov <vladbu@mellanox.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, mleitner@redhat.com,
paulb@mellanox.com
Subject: Re: [PATCH iproute2 net] tc: remove duplicated NEXT_ARG_FWD() in parse_ct()
Date: Fri, 1 Nov 2019 09:37:26 -0700 [thread overview]
Message-ID: <20191101093726.6c867e96@hermes.lan> (raw)
In-Reply-To: <20191029175346.14564-1-vladbu@mellanox.com>
On Tue, 29 Oct 2019 19:53:46 +0200
Vlad Buslov <vladbu@mellanox.com> wrote:
> Function parse_ct() manually calls NEXT_ARG_FWD() after
> parse_action_control_dflt(). This is redundant because
> parse_action_control_dflt() modifies argc and argv itself. Moreover, such
> implementation parses out any following actions option. For example, adding
> action ct with cookie errors:
>
> $ sudo tc actions add action ct cookie 111111111111
> Bad action type 111111111111
> Usage: ... gact <ACTION> [RAND] [INDEX]
> Where: ACTION := reclassify | drop | continue | pass | pipe |
> goto chain <CHAIN_INDEX> | jump <JUMP_COUNT>
> RAND := random <RANDTYPE> <ACTION> <VAL>
> RANDTYPE := netrand | determ
> VAL : = value not exceeding 10000
> JUMP_COUNT := Absolute jump from start of action list
> INDEX := index value used
>
> With fix:
>
> $ sudo tc actions add action ct cookie 111111111111
> $ sudo tc actions list action ct
> total acts 1
>
> action order 0: ct zone 0 pipe
> index 1 ref 1 bind 0
> cookie 111111111111
>
> Fixes: c8a494314c40 ("tc: Introduce tc ct action")
> Signed-off-by: Vlad Buslov <vladbu@mellanox.com>
Applied
prev parent reply other threads:[~2019-11-01 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 17:53 [PATCH iproute2 net] tc: remove duplicated NEXT_ARG_FWD() in parse_ct() Vlad Buslov
2019-10-29 18:08 ` Marcelo Ricardo Leitner
2019-11-01 16:37 ` 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=20191101093726.6c867e96@hermes.lan \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=paulb@mellanox.com \
--cc=vladbu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.