From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH nf-next 00/12,v2] register tracking infrastructure follow up
Date: Mon, 14 Mar 2022 01:54:05 +0100 [thread overview]
Message-ID: <20220314005417.315832-1-pablo@netfilter.org> (raw)
Hi,
The following patchset follows up on the register tracking infrastructure:
1) Add NFT_REDUCE_READONLY pointer cookie and use it, this is used
to describe expressions that perform read-only operations on registers.
Add WARN_ON_ONCE() to check for expr->ops->reduce, all expressions
must have one.
v2: add missing ipv4 and ipv6 expressions. simplify cookie logic
2) Cancel register tracking information for operations that are larger
than 32-bits (one register). Add update/cancel helper functions and
adapt existing code to use them.
v2: track partial clobbering. add nft_reg_track_cmp()
3) Add .reduce support to nft_ct.
4) Add .reduce support to nft_lookup.
5) Add .reduce support for nft_meta_bridge.
6) Add .reduce support for nft_numgen.
7) Add .reduce support for nft_osf.
8) Add .reduce support for nft_hash (jhash and symhash)
9) Add .reduce support for nft_immediate
10) Add .reduce support for nft_socket
11) Add .reduce support for nft_xfrm
12) Add .reduce support for nft_tunnel
Missing expressions with no expr->ops->reduce after this round:
- exthdr
- fib
Florian Westphal (2):
netfilter: nft_lookup: only cancel tracking for clobbered dregs
netfilter: nft_meta: extend reduce support to bridge family
Pablo Neira Ayuso (10):
netfilter: nf_tables: do not reduce read-only expressions
netfilter: nf_tables: cancel tracking for clobbered destination registers
netfilter: nft_ct: track register operations
netfilter: nft_numgen: cancel register tracking
netfilter: nft_osf: track register operations
netfilter: nft_hash: track register operations
netfilter: nft_immediate: cancel register tracking for data destination register
netfilter: nft_socket: track register operations
netfilter: nft_xfrm: track register operations
netfilter: nft_tunnel: track register operations
include/net/netfilter/nf_tables.h | 22 ++++++++
include/net/netfilter/nft_meta.h | 3 ++
net/bridge/netfilter/nft_meta_bridge.c | 5 +-
net/bridge/netfilter/nft_reject_bridge.c | 1 +
net/ipv4/netfilter/nft_dup_ipv4.c | 1 +
net/ipv4/netfilter/nft_reject_ipv4.c | 1 +
net/ipv6/netfilter/nft_dup_ipv6.c | 1 +
net/ipv6/netfilter/nft_reject_ipv6.c | 1 +
net/netfilter/nf_tables_api.c | 69 +++++++++++++++++++++++-
net/netfilter/nft_bitwise.c | 24 ++++++---
net/netfilter/nft_byteorder.c | 3 +-
net/netfilter/nft_cmp.c | 3 ++
net/netfilter/nft_compat.c | 1 +
net/netfilter/nft_connlimit.c | 1 +
net/netfilter/nft_counter.c | 1 +
net/netfilter/nft_ct.c | 48 +++++++++++++++++
net/netfilter/nft_dup_netdev.c | 1 +
net/netfilter/nft_dynset.c | 1 +
net/netfilter/nft_flow_offload.c | 1 +
net/netfilter/nft_fwd_netdev.c | 2 +
net/netfilter/nft_hash.c | 36 +++++++++++++
net/netfilter/nft_immediate.c | 12 +++++
net/netfilter/nft_last.c | 1 +
net/netfilter/nft_limit.c | 2 +
net/netfilter/nft_log.c | 1 +
net/netfilter/nft_lookup.c | 12 +++++
net/netfilter/nft_masq.c | 3 ++
net/netfilter/nft_meta.c | 19 ++++---
net/netfilter/nft_nat.c | 2 +
net/netfilter/nft_numgen.c | 22 ++++++++
net/netfilter/nft_objref.c | 2 +
net/netfilter/nft_osf.c | 25 +++++++++
net/netfilter/nft_payload.c | 12 ++---
net/netfilter/nft_queue.c | 2 +
net/netfilter/nft_quota.c | 1 +
net/netfilter/nft_range.c | 1 +
net/netfilter/nft_redir.c | 3 ++
net/netfilter/nft_reject_inet.c | 1 +
net/netfilter/nft_reject_netdev.c | 1 +
net/netfilter/nft_rt.c | 1 +
net/netfilter/nft_socket.c | 28 ++++++++++
net/netfilter/nft_synproxy.c | 1 +
net/netfilter/nft_tproxy.c | 1 +
net/netfilter/nft_tunnel.c | 28 ++++++++++
net/netfilter/nft_xfrm.c | 28 ++++++++++
45 files changed, 403 insertions(+), 32 deletions(-)
--
2.30.2
next reply other threads:[~2022-03-14 0:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 0:54 Pablo Neira Ayuso [this message]
2022-03-14 0:54 ` [PATCH nf-next 01/12,v2] netfilter: nf_tables: do not reduce read-only expressions Pablo Neira Ayuso
2022-03-14 7:35 ` kernel test robot
2022-03-14 0:54 ` [PATCH nf-next 02/12,v2] netfilter: nf_tables: cancel tracking for clobbered destination registers Pablo Neira Ayuso
2022-03-14 10:38 ` kernel test robot
2022-03-14 0:54 ` [PATCH nf-next 03/12,v2] netfilter: nft_ct: track register operations Pablo Neira Ayuso
2022-03-14 0:54 ` [PATCH nf-next 04/12,v2] netfilter: nft_lookup: only cancel tracking for clobbered dregs Pablo Neira Ayuso
2022-03-14 0:54 ` [PATCH nf-next 05/12,v2] netfilter: nft_meta: extend reduce support to bridge family Pablo Neira Ayuso
2022-03-14 0:54 ` [PATCH nf-next 06/12,v2] netfilter: nft_numgen: cancel register tracking Pablo Neira Ayuso
2022-03-14 0:54 ` [PATCH nf-next 07/12,v2] netfilter: nft_osf: track register operations Pablo Neira Ayuso
2022-03-14 0:54 ` [PATCH nf-next 08/12,v2] netfilter: nft_hash: " Pablo Neira Ayuso
2022-03-14 0:54 ` [PATCH nf-next 09/12,v2] netfilter: nft_immediate: cancel register tracking for data destination register Pablo Neira Ayuso
2022-03-14 0:54 ` [PATCH nf-next 10/12,v2] netfilter: nft_socket: track register operations Pablo Neira Ayuso
2022-03-14 0:54 ` [PATCH nf-next 11/12,v2] netfilter: nft_xfrm: " Pablo Neira Ayuso
2022-03-14 0:54 ` [PATCH nf-next 12/12,v2] netfilter: nft_tunnel: " 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=20220314005417.315832-1-pablo@netfilter.org \
--to=pablo@netfilter.org \
--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).