netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nf-next 0/4] netfilter: remove obsolete hook wrappers
Date: Mon, 11 Oct 2021 17:15:09 +0200	[thread overview]
Message-ID: <20211011151514.6580-1-fw@strlen.de> (raw)

An earlier series, starting with
commit a4aeafa28cf706f65f ("netfilter: xt_nat: pass table to hookfn"),
converted the x_tables table implementations to store the hook blob in
the ->priv pointer that gets passed to the hook function.

Before this, the blobs were stored in struct net, so each table
required its own wrapper to fetch the correct table blob.

Nowadays, allmost all hook functions in x_table land just call the hook
evaluation loop.

This series converts the table evaluation loop so it can be used directly,
then removes most of the wrappers.

Florian Westphal (4):
  netfilter: iptables: allow use of ipt_do_table as hookfn
  netfilter: arp_tables: allow use of arpt_do_table as hookfn
  netfilter: ip6tables: allow use of ip6t_do_table as hookfn
  netfilter: ebtables: allow use of ebt_do_table as hookfn

 include/linux/netfilter_arp/arp_tables.h  |  5 ++---
 include/linux/netfilter_bridge/ebtables.h |  5 ++---
 include/linux/netfilter_ipv4/ip_tables.h  |  6 +++---
 include/linux/netfilter_ipv6/ip6_tables.h |  5 ++---
 net/bridge/netfilter/ebtable_broute.c     |  2 +-
 net/bridge/netfilter/ebtable_filter.c     | 13 +++----------
 net/bridge/netfilter/ebtable_nat.c        | 12 +++---------
 net/bridge/netfilter/ebtables.c           |  6 +++---
 net/ipv4/netfilter/arp_tables.c           |  7 ++++---
 net/ipv4/netfilter/arptable_filter.c      | 10 +---------
 net/ipv4/netfilter/ip_tables.c            |  7 ++++---
 net/ipv4/netfilter/iptable_filter.c       |  9 +--------
 net/ipv4/netfilter/iptable_mangle.c       |  8 ++++----
 net/ipv4/netfilter/iptable_nat.c          | 15 ++++-----------
 net/ipv4/netfilter/iptable_raw.c          | 10 +---------
 net/ipv4/netfilter/iptable_security.c     |  9 +--------
 net/ipv6/netfilter/ip6_tables.c           |  6 +++---
 net/ipv6/netfilter/ip6table_filter.c      | 10 +---------
 net/ipv6/netfilter/ip6table_mangle.c      |  8 ++++----
 net/ipv6/netfilter/ip6table_nat.c         | 15 ++++-----------
 net/ipv6/netfilter/ip6table_raw.c         | 10 +---------
 net/ipv6/netfilter/ip6table_security.c    |  9 +--------
 22 files changed, 53 insertions(+), 134 deletions(-)

-- 
2.32.0


             reply	other threads:[~2021-10-11 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 15:15 Florian Westphal [this message]
2021-10-11 15:15 ` [PATCH nf-next 1/4] netfilter: iptables: allow use of ipt_do_table as hookfn Florian Westphal
2021-10-11 15:15 ` [PATCH nf-next 1/4] netfilter: ipv4: " Florian Westphal
2021-10-11 15:15 ` [PATCH nf-next 2/4] netfilter: arp_tables: allow use of arpt_do_table " Florian Westphal
2021-10-11 15:15 ` [PATCH nf-next 3/4] netfilter: ip6tables: allow use of ip6t_do_table " Florian Westphal
2021-10-11 15:15 ` [PATCH nf-next 4/4] netfilter: ebtables: allow use of ebt_do_table " Florian Westphal
2021-10-14 21:02 ` [PATCH nf-next 0/4] netfilter: remove obsolete hook wrappers Pablo Neira Ayuso

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=20211011151514.6580-1-fw@strlen.de \
    --to=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    /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).