From: Jozsef Kadlecsik <kadlec@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: Pablo Neira Ayuso <pablo@netfilter.org>
Subject: [PATCH 0/1] ipset patch for the nf-next tree
Date: Tue, 22 Nov 2022 20:30:56 +0100 [thread overview]
Message-ID: <20221122193057.1052032-1-kadlec@netfilter.org> (raw)
Hi Pablo,
Please apply the next patch to your nf-next tree, which introduces a new feature
in ipset:
- The patch adds the new "bitmask" parameter to the hash:ip, hash:ip,port and
hash:net,net types. While the existing "netmask" parameter accepts only valid
netmask values, "bitmask" takes any arbitrary IP address and makes possible
to mask out arbitrary bits. Patch is from Vishwanath Pai.
Best regards,
Jozsef
The following changes since commit ab0377803dafc58f1e22296708c1c28e309414d6:
mrp: introduce active flags to prevent UAF when applicant uninit (2022-11-18 12:14:55 +0000)
are available in the Git repository at:
git://blackhole.kfki.hu/nf-next b16269331983edf64f
for you to fetch changes up to b16269331983edf64ff0c4a5286b900502a362a8:
netfilter: ipset: Add support for new bitmask parameter (2022-11-22 20:21:11 +0100)
----------------------------------------------------------------
Vishwanath Pai (1):
netfilter: ipset: Add support for new bitmask parameter
include/linux/netfilter/ipset/ip_set.h | 10 ++++
include/uapi/linux/netfilter/ipset/ip_set.h | 2 +
net/netfilter/ipset/ip_set_hash_gen.h | 71 +++++++++++++++++++++++++----
net/netfilter/ipset/ip_set_hash_ip.c | 19 ++++----
net/netfilter/ipset/ip_set_hash_ipport.c | 24 +++++++++-
net/netfilter/ipset/ip_set_hash_netnet.c | 26 +++++++++--
6 files changed, 126 insertions(+), 26 deletions(-)
next reply other threads:[~2022-11-22 19:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 19:30 Jozsef Kadlecsik [this message]
2022-11-22 19:30 ` [PATCH 1/1] netfilter: ipset: Add support for new bitmask parameter Jozsef Kadlecsik
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=20221122193057.1052032-1-kadlec@netfilter.org \
--to=kadlec@netfilter.org \
--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).