[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAM_iQpWkoSpWQipShKZP-J-7n79VHa+h5ibbdp0P28mYe7c_GA@mail.gmail.com>
Date: Fri, 19 May 2017 09:50:51 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Sabrina Dubroca <sd@...asysnail.net>
Cc: Linux Kernel Network Developers <netdev@...r.kernel.org>,
Jiri Pirko <jiri@...lanox.com>,
Jamal Hadi Salim <jhs@...atatu.com>
Subject: Re: [PATCH net-next] net: sched: provide stubs for
tcf_chain_{get,put} for CONFIG_NET_CLS=n
On Thu, May 18, 2017 at 9:24 AM, Sabrina Dubroca <sd@...asysnail.net> wrote:
> This also changes tcf_chain_get() to return an error pointer instead of
> NULL, so that tcf_action_goto_chain_init() can differentiate memory
> allocation failure from lack of support.
>
> Fixes: 5bc1701881e3 ("net: sched: introduce multichain support for filters")
> Signed-off-by: Sabrina Dubroca <sd@...asysnail.net>
> ---
> I'm not sure this EOPNOTSUPP is really necessary, ie if we can really
> reach the tcf_action_goto_chain_init() call when CONFIG_NET_CLS=n.
> If not, a simpler patch would add a tcf_chain_get() stub that just
> returns NULL, as we wouldn't have to care about returning an incorrect
> error code from tcf_action_goto_chain_init().
I wonder if we should just make CONFIG_NET_CLS_ACT depending
on CONFIG_NET_CLS. Although without filters we can still have
standalone actions but no one can use them.
Powered by blists - more mailing lists