From: Stefano Brivio <sbrivio@redhat.com>
To: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Cc: "Florian Westphal" <fw@strlen.de>,
"Kadlecsik József" <kadlec@blackhole.kfki.hu>,
"Eric Garver" <eric@garver.life>, "Phil Sutter" <phil@nwl.cc>
Subject: [PATCH libnftnl v4 0/3] Attributes for concatenated ranges
Date: Thu, 30 Jan 2020 01:16:31 +0100 [thread overview]
Message-ID: <cover.1580342940.git.sbrivio@redhat.com> (raw)
This series adds support for NFTA_SET_DESC_CONCAT set attribute and
the additional key passed as NFTA_SET_ELEM_KEY_END to denote the
upper bound of a range in a generic way, as suggested by Pablo.
v4: Sync nf_tables.h header, move NFTNL_SET_DESC_CONCAT to avoid
ABI breakage (Pablo Neira Ayuso)
v3: Support for separate "end" key added as 2/2, reworked 1/2 to
use set description data for length of concatenation fields
Stefano Brivio (3):
include: resync nf_tables.h cache copy
set: Add support for NFTA_SET_DESC_CONCAT attributes
set_elem: Introduce support for NFTNL_SET_ELEM_KEY_END
include/libnftnl/set.h | 2 +
include/linux/netfilter/nf_tables.h | 17 +++++
include/set.h | 2 +
include/set_elem.h | 1 +
src/set.c | 111 +++++++++++++++++++++++-----
src/set_elem.c | 24 ++++++
6 files changed, 138 insertions(+), 19 deletions(-)
--
2.24.1
next reply other threads:[~2020-01-30 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 0:16 Stefano Brivio [this message]
2020-01-30 0:16 ` [PATCH libnftnl v4 1/3] include: resync nf_tables.h cache copy Stefano Brivio
2020-01-30 0:16 ` [PATCH libnftnl v4 2/3] set: Add support for NFTA_SET_DESC_CONCAT attributes Stefano Brivio
2020-01-30 0:16 ` [PATCH libnftnl v4 3/3] set_elem: Introduce support for NFTNL_SET_ELEM_KEY_END Stefano Brivio
2020-02-05 15:01 ` [PATCH libnftnl v4 0/3] Attributes for concatenated ranges 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=cover.1580342940.git.sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=eric@garver.life \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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).