From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Cc: Florian Westphal <fw@strlen.de>
Subject: [PATCH nf-next 0/2] netfilter: new hook nfnl subsystem
Date: Tue, 1 Jun 2021 18:21:34 +0200 [thread overview]
Message-ID: <20210601162136.19444-1-fw@strlen.de> (raw)
First patch is a required dependency to allow to check when
its safe to treat the 'priv' pointer as a nft base chain pointer.
Second patch adds a new nfnl subsystem to enable userspace to dump
the active hooks to userspace.
Previous patches added this to nf_tables instead, but technically
this isn't related to nf_tables.
Using a new nfnl subsys allows to extend this later, e.g. to
send out notifications, e.g. when a new base hook is registered.
Florian Westphal (2):
netfilter: annotate nf_tables base hook ops
netfilter: add new hook nfnl subsystem
include/linux/netfilter.h | 8 +-
include/uapi/linux/netfilter/nfnetlink.h | 3 +-
include/uapi/linux/netfilter/nfnetlink_hook.h | 54 +++
net/netfilter/Kconfig | 9 +
net/netfilter/Makefile | 1 +
net/netfilter/nf_tables_api.c | 4 +-
net/netfilter/nfnetlink_hook.c | 375 ++++++++++++++++++
7 files changed, 451 insertions(+), 3 deletions(-)
create mode 100644 include/uapi/linux/netfilter/nfnetlink_hook.h
create mode 100644 net/netfilter/nfnetlink_hook.c
--
2.26.3
next reply other threads:[~2021-06-01 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 16:21 Florian Westphal [this message]
2021-06-01 16:21 ` [PATCH nf-next 1/2] netfilter: annotate nf_tables base hook ops Florian Westphal
2021-06-01 16:21 ` [PATCH nf-next 2/2] netfilter: add new hook nfnl subsystem Florian Westphal
2021-06-04 3:00 ` [netfilter] a0aa657b74: WARNING:at_kernel/locking/lockdep.c:#lockdep_init_map_type kernel test robot
2021-06-04 5:46 ` Florian Westphal
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=20210601162136.19444-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).