[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170626165309.GM29636@breakpoint.cc>
Date: Mon, 26 Jun 2017 18:53:09 +0200
From: Florian Westphal <fw@...len.de>
To: Lin Zhang <xiaolou4617@...il.com>
Cc: pablo@...filter.org, kadlec@...ckhole.kfki.hu, fw@...len.de,
davem@...emloft.net, linux-kernel@...r.kernel.org,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org
Subject: Re: [PATCH net-next] netfilter: conntrack: add a new
NF_CT_EXT_EXPAND extension
Lin Zhang <xiaolou4617@...il.com> wrote:
> In the current conntrack extend code, if we want to add a new
> extension, we must be add a new extension id and recompile kernel.
> I think that is not be convenient for users, so i add a new extension named
> NF_CT_EXT_EXPAND for supporting dynamic register/unregister expansion
> in runtime that means if kernel support NF_CT_EXT_EXPAND extension,
> user could call nf_ct_expand_area_add() to register a new expansion
> but not need to predefine an id in enum nf_ct_ext_id.
We never did this because its only required for out of tree modules.
I would prefer if such extensions are discussed/proposed on nf-devel
instead, and then, if there is agreement that the extension is useful,
it can be submitted for inclusion in mainline kernel instead.
Powered by blists - more mailing lists