[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161026112302.7d7fecd0@xeon-e3>
Date: Wed, 26 Oct 2016 11:23:02 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Shmulik Ladkani <shmulik.ladkani@...il.com>
Cc: Jamal Hadi Salim <jhs@...atatu.com>, netdev@...r.kernel.org
Subject: Re: [PATCH iproute2 net-next] tc: m_mirred: Fix parsing of 'index'
optional argument
On Fri, 21 Oct 2016 23:01:15 +0300
Shmulik Ladkani <shmulik.ladkani@...il.com> wrote:
> Code in parse_mirred() suggests "index" argument can be placed either
> after the "egress" clause, or as the first argument (after "action mirred").
>
> However, parse_egress() fails to correctly parse "index" if it's the
> first argument.
>
> For example:
>
> # tc filter add ... action mirred index 5
> RTNETLINK answers: Invalid argument
> (unnecessary RTNETLINK issued, should have been parse error)
>
> # tc filter add ... action mirred index 5 egress redirect dev eth0
> bad action type egress
> (should have been parsed successfully)
>
> Fix parse_egress as follows:
> - continue parsing after valid "index" is seen
> - don't issue the RTNETLINK unless valid "egress" is seen
>
> Signed-off-by: Shmulik Ladkani <shmulik.ladkani@...il.com>
Looks like a good fix but does not apply cleanly to current net-next branch.
Please cleanup and resubmit.
Powered by blists - more mailing lists