netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
To: netfilter-devel@vger.kernel.org
Cc: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Subject: [iptables-nftables - RFC v2 PATCH  16/17] nft: Add a function to reset the counters of an existing rule
Date: Thu, 25 Jul 2013 20:16:36 +0300	[thread overview]
Message-ID: <1374772597-20548-17-git-send-email-tomasz.bursztyka@linux.intel.com> (raw)
In-Reply-To: <1374772597-20548-1-git-send-email-tomasz.bursztyka@linux.intel.com>

Now that we parse properly, in one place and at once, the rule back into a 
command structure, it's now easier to reset its counters from that command
structure which we can pass again to nft_rule_append. (Thus the rule will
be replaced since we provide it's handle.)


Signed-off-by: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
---
 iptables/nft.c | 35 +++++++++++++++++++++++++++++++++++
 iptables/nft.h |  1 +
 2 files changed, 36 insertions(+)

diff --git a/iptables/nft.c b/iptables/nft.c
index d05f6ae..2b17e37 100644
--- a/iptables/nft.c
+++ b/iptables/nft.c
@@ -2298,6 +2298,41 @@ err:
 	return ret;
 }
 
+int nft_rule_zero_counters(struct nft_handle *h, const char *chain,
+			   const char *table, int rulenum)
+{
+	struct iptables_command_state cs = {};
+	struct nft_rule_list *list;
+	struct nft_rule *r;
+	int ret = 0;
+
+	nft_fn = nft_rule_delete;
+
+	list = nft_rule_list_create(h);
+	if (list == NULL)
+		return 0;
+
+	r = nft_rule_find(list, chain, table, NULL, rulenum);
+	if (r == NULL) {
+		errno = ENOENT;
+		ret = 1;
+
+		goto error;
+	}
+
+	nft_rule_to_iptables_command_state(r, &cs);
+
+	cs.counters.pcnt = cs.counters.bcnt = 0;
+
+	ret =  nft_rule_append(h, chain, table, &cs,
+			nft_rule_attr_get_u64(r, NFT_RULE_ATTR_HANDLE), false);
+
+error:
+	nft_rule_list_destroy(list);
+
+	return ret;
+}
+
 static int nft_action(struct nft_handle *h, int type)
 {
 	char buf[MNL_SOCKET_BUFFER_SIZE];
diff --git a/iptables/nft.h b/iptables/nft.h
index c904e21..31e1083 100644
--- a/iptables/nft.h
+++ b/iptables/nft.h
@@ -59,6 +59,7 @@ int nft_rule_list(struct nft_handle *h, const char *chain, const char *table, in
 int nft_rule_list_save(struct nft_handle *h, const char *chain, const char *table, int rulenum, int counters);
 int nft_rule_save(struct nft_handle *h, const char *table, bool counters);
 int nft_rule_flush(struct nft_handle *h, const char *chain, const char *table);
+int nft_rule_zero_counters(struct nft_handle *h, const char *chain, const char *table, int rulenum);
 
 enum nft_rule_print {
 	NFT_RULE_APPEND,
-- 
1.8.3.2


  parent reply	other threads:[~2013-07-25 17:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 17:16 [iptables-nftables - RFC v2 PATCH 00/17] Xtables extensions: full support (pure nft or compat layer) Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 01/17] nft: Remove useless function Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 02/17] xtables: Add support for injecting xtables target into nft rule Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 03/17] xtables: add support for injecting xtables matches " Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 04/17] nft: Add nft expressions translation engine as a library Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 05/17] nft: Integrate nft translator engine in current core Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 06/17] nft: Manage xtables target parsing through translation tree Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 07/17] nft: Manage xtables matches through nft " Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 08/17] nft: Add support for xtables extensions callback to change cs Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 09/17] xtables: Add support for registering nft translation function for target Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 10/17] xtables: Add support for registering nft translation function for match Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 11/17] nft: Register all relevant xtables extensions into translation tree Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 12/17] nft: Refactor firewall printing so it reuses already parsed cs struct Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 13/17] nft: Refactor rule deletion so it compares both cs structure Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 14/17] xtables: nft: Complete refactoring on how rules are saved Tomasz Bursztyka
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 15/17] xtables: Support pure nft expressions for DNAT extension Tomasz Bursztyka
2013-07-25 17:16 ` Tomasz Bursztyka [this message]
2013-07-25 17:16 ` [iptables-nftables - RFC v2 PATCH 17/17] xtables: Support -Z options for a given rule number Tomasz Bursztyka

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=1374772597-20548-17-git-send-email-tomasz.bursztyka@linux.intel.com \
    --to=tomasz.bursztyka@linux.intel.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).