From: Ana Rey <anarey@gmail.com>
To: netfilter-devel@vger.kernel.org
Cc: Ana Rey <anarey@gmail.com>
Subject: [libnftnl PATCH 1/4] expr: ct: Use nft_rule_expr_set_* in the xml parsing code
Date: Tue, 24 Jun 2014 08:46:37 +0200 [thread overview]
Message-ID: <1403592401-5057-2-git-send-email-anarey@gmail.com> (raw)
In-Reply-To: <1403592401-5057-1-git-send-email-anarey@gmail.com>
Code refactoring to use nft_rule_expr_set_* in parse functions
Signed-off-by: Ana Rey <anarey@gmail.com>
---
src/expr/ct.c | 22 ++++++++--------------
1 file changed, 8 insertions(+), 14 deletions(-)
diff --git a/src/expr/ct.c b/src/expr/ct.c
index 38f5169..0f1c050 100644
--- a/src/expr/ct.c
+++ b/src/expr/ct.c
@@ -286,23 +286,18 @@ static int nft_rule_expr_ct_xml_parse(struct nft_rule_expr *e, mxml_node_t *tree
struct nft_parse_err *err)
{
#ifdef XML_PARSING
- struct nft_expr_ct *ct = nft_expr_data(e);
const char *key_str, *dir_str;
int key;
uint8_t dir;
- uint32_t reg;
+ uint32_t dreg, sreg;
- if (nft_mxml_reg_parse(tree, "dreg", ®, MXML_DESCEND_FIRST,
- NFT_XML_OPT, err) >= 0) {
- ct->dreg = reg;
- e->flags |= (1 << NFT_EXPR_CT_DREG);
- }
+ if (nft_mxml_reg_parse(tree, "dreg", &dreg, MXML_DESCEND_FIRST,
+ NFT_XML_OPT, err) >= 0)
+ nft_rule_expr_set_u32(e, NFT_EXPR_CT_DREG, dreg);
- if (nft_mxml_reg_parse(tree, "sreg", ®, MXML_DESCEND_FIRST,
- NFT_XML_OPT, err) >= 0) {
- ct->sreg = reg;
- e->flags |= (1 << NFT_EXPR_CT_SREG);
- }
+ if (nft_mxml_reg_parse(tree, "sreg", &sreg, MXML_DESCEND_FIRST,
+ NFT_XML_OPT, err) >= 0)
+ nft_rule_expr_set_u32(e, NFT_EXPR_CT_SREG, sreg);
key_str = nft_mxml_str_parse(tree, "key", MXML_DESCEND_FIRST,
NFT_XML_MAND, err);
@@ -313,8 +308,7 @@ static int nft_rule_expr_ct_xml_parse(struct nft_rule_expr *e, mxml_node_t *tree
if (key < 0)
goto err;
- ct->key = key;
- e->flags |= (1 << NFT_EXPR_CT_KEY);
+ nft_rule_expr_set_u32(e, NFT_EXPR_CT_KEY, key);
dir_str = nft_mxml_str_parse(tree, "dir", MXML_DESCEND_FIRST,
NFT_XML_OPT, err);
--
2.0.0
next prev parent reply other threads:[~2014-06-24 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 6:46 [libnftnl PATCH 0/4] expr: ct: Do not print unset values in xml and json Ana Rey
2014-06-24 6:46 ` Ana Rey [this message]
2014-06-24 6:46 ` [libnftnl PATCH 2/4] expr: ct: Do not print unset values in xml file Ana Rey
2014-06-24 6:46 ` [libnftnl PATCH 3/4] expr: ct: Delete the last comma character in json text Ana Rey
2014-06-24 6:46 ` [libnftnl PATCH 4/4] expr: ct: Do not print unset values in json Ana Rey
2014-06-24 6:46 ` Ana Rey
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=1403592401-5057-2-git-send-email-anarey@gmail.com \
--to=anarey@gmail.com \
--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).