From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Florian Westphal <fw@strlen.de>, netfilter-devel@vger.kernel.org
Subject: [nf-next PATCH v4 0/3] Introduce locking for rule reset requests
Date: Thu, 19 Oct 2023 16:03:33 +0200 [thread overview]
Message-ID: <20231019140336.31563-1-phil@nwl.cc> (raw)
Extracted series from the previous v2 of "Introduce locking for reset
requests". If consensus is reached over the implementation details,
respective series for object and set element reset follow.
Changes since v2:
- Aim at nf-next with this.
- Refactoring of nft_rule_dump_ctx already accepted.
- New patch 1 streamlining the changes in the remaining patches.
- Some reorg of local variables.
Changes since v3:
- Use '%.*s' format specifier as suggested by Florian.
- Add a comment as suggested by Pablo.
Phil Sutter (3):
netfilter: nf_tables: Open-code audit log call in nf_tables_getrule()
netfilter: nf_tables: Introduce nf_tables_getrule_single()
netfilter: nf_tables: Add locking for NFT_MSG_GETRULE_RESET requests
net/netfilter/nf_tables_api.c | 144 +++++++++++++++++++++++++---------
1 file changed, 109 insertions(+), 35 deletions(-)
--
2.41.0
next reply other threads:[~2023-10-19 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 14:03 Phil Sutter [this message]
2023-10-19 14:03 ` [nf-next PATCH v4 1/3] netfilter: nf_tables: Open-code audit log call in nf_tables_getrule() Phil Sutter
2023-10-25 9:46 ` Pablo Neira Ayuso
2023-10-19 14:03 ` [nf-next PATCH v4 2/3] netfilter: nf_tables: Introduce nf_tables_getrule_single() Phil Sutter
2023-10-19 14:03 ` [nf-next PATCH v4 3/3] netfilter: nf_tables: Add locking for NFT_MSG_GETRULE_RESET requests Phil Sutter
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=20231019140336.31563-1-phil@nwl.cc \
--to=phil@nwl.cc \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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).