[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180730142155.GC10626@nanopsycho>
Date: Mon, 30 Jul 2018 16:21:55 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
Cong Wang <xiyou.wangcong@...il.com>,
Daniel Borkmann <daniel@...earbox.net>,
Marcelo Ricardo Leitner <marcelo.leitner@...il.com>,
Eyal Birger <eyal.birger@...il.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: [PATCH net-next v5 1/4] net/sched: user-space can't set unknown
tcfa_action values
Mon, Jul 30, 2018 at 04:03:50PM CEST, jhs@...atatu.com wrote:
>On 30/07/18 08:30 AM, Paolo Abeni wrote:
>> }
>> + if (!tcf_action_valid(a->tcfa_action)) {
>> + NL_SET_ERR_MSG(extack, "invalid action value, using TC_ACT_UNSPEC instead");
>> + a->tcfa_action = TC_ACT_UNSPEC;
>> + }
>> +
>> return a;
>
>
>I think it would make a lot more sense to just reject the entry than
>changing it underneath the user to a default value. Least element of
>suprise.
It might break existing user who is incorrectly doing it. But I'm okay
with both solutions.
>
>cheers,
>jamal
Powered by blists - more mailing lists