From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Shmulik Ladkani <shmulik@nsof.io>
Cc: netfilter-devel@vger.kernel.org,
Willem de Bruijn <willemb@google.com>,
rbk@nsof.io, Rafael Buchbinder <rafi@rbk.ms>
Subject: Re: [PATCH v2 1/2] iptables: support match info fixup after tc_init
Date: Mon, 18 Sep 2017 18:28:11 +0200 [thread overview]
Message-ID: <20170918162811.GA6091@salvia> (raw)
In-Reply-To: <20170917112031.8644-2-shmulik@nsof.io>
Hi Rafael,
On Sun, Sep 17, 2017 at 02:20:30PM +0300, Shmulik Ladkani wrote:
> From: Rafael Buchbinder <rafi@rbk.ms>
>
> From: Rafael Buchbinder <rafi@rbk.ms>
>
> This commit introduces a framework to fixup match info,
> which may be required by an extension.
>
> Signed-off-by: Rafael Buchbinder <rafi@rbk.ms>
> Signed-off-by: Shmulik Ladkani <shmulik@nsof.io>
> ---
> include/xtables.h | 3 +++
> iptables/ip6tables.c | 35 +++++++++++++++++++++++++++++++++++
> iptables/iptables.c | 34 ++++++++++++++++++++++++++++++++++
> 3 files changed, 72 insertions(+)
>
> diff --git a/include/xtables.h b/include/xtables.h
> index e9bc3b7d..687cfe9f 100644
> --- a/include/xtables.h
> +++ b/include/xtables.h
> @@ -273,6 +273,9 @@ struct xtables_match {
> /* ip is struct ipt_ip * for example */
> void (*save)(const void *ip, const struct xt_entry_match *match);
>
> + /* Fixes the match info after init. */
> + void (*tc_init_fixup)(struct xt_entry_match *match);
If this is only broken from tc ipt actions, could you fix this from
iproute2/tc instead?
next prev parent reply other threads:[~2017-09-18 16:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 11:20 [PATCH v2 0/2] xt_bpf: fix handling of pinned objects Shmulik Ladkani
2017-09-17 11:20 ` [PATCH v2 1/2] iptables: support match info fixup after tc_init Shmulik Ladkani
2017-09-18 16:28 ` Pablo Neira Ayuso [this message]
2017-09-18 17:00 ` Shmulik Ladkani
2017-09-18 17:23 ` Pablo Neira Ayuso
2017-09-18 17:50 ` Willem de Bruijn
2017-09-18 17:54 ` Pablo Neira Ayuso
2017-10-04 14:33 ` Pablo Neira Ayuso
2017-10-04 14:38 ` Shmulik Ladkani
2017-09-18 18:04 ` Jan Engelhardt
2017-09-17 11:20 ` [PATCH v2 2/2] extensions: xt_bpf: get the pinned ebpf object when match is initialized Shmulik Ladkani
2017-09-18 16:22 ` Willem de Bruijn
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=20170918162811.GA6091@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=rafi@rbk.ms \
--cc=rbk@nsof.io \
--cc=shmulik@nsof.io \
--cc=willemb@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).