From: Patrick McHardy <kaber@trash.net>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 0/2] set: set parsing fixes
Date: Thu, 16 Jan 2014 20:16:24 +0000 [thread overview]
Message-ID: <1389903386-20612-1-git-send-email-kaber@trash.net> (raw)
The following two patches fix a couple of problems with printed set
outputs from "nft list table ..." and parsing the output again with
"nft -f".
- internal flags are printed
- flags are not parsable
- initializers (elements = { }) is not parsable
With these patches, parsing the output of "nft list table ..." works
in at least more cases than before when sets are present. We still
have ordering problems, verdict maps referencing chains will fail
since chains are created after the maps. The same problem exists
generally for jump rules.
Changes to last version: set data type and evaluate initializers.
These patches have been tested to work as described. I'll push them
to master now.
next reply other threads:[~2014-01-16 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 20:16 Patrick McHardy [this message]
2014-01-16 20:16 ` [PATCH 1/2] set: make set flags output parsable Patrick McHardy
2014-01-16 20:16 ` [PATCH 2/2] set: make set initializer parsable Patrick McHardy
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=1389903386-20612-1-git-send-email-kaber@trash.net \
--to=kaber@trash.net \
--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).