From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Cc: kaber@trash.net
Subject: [PATCH 3/3 iptables,xlate4] xtables: add xt_xlate_add_comment()
Date: Mon, 1 Feb 2016 19:43:36 +0100 [thread overview]
Message-ID: <1454352216-18812-3-git-send-email-pablo@netfilter.org> (raw)
In-Reply-To: <1454352216-18812-1-git-send-email-pablo@netfilter.org>
This new function allows us to add comments to the nft rule. This
can be used to provide a translation for the comment match.
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---
include/xtables.h | 1 +
libxtables/xtables.c | 41 ++++++++++++++++++++++++++---------------
2 files changed, 27 insertions(+), 15 deletions(-)
diff --git a/include/xtables.h b/include/xtables.h
index 82aa2bb..6fd3bdf 100644
--- a/include/xtables.h
+++ b/include/xtables.h
@@ -573,6 +573,7 @@ extern const char *xtables_lmap_id2name(const struct xtables_lmap *, int);
struct xt_xlate *xt_xlate_alloc(int size);
void xt_xlate_free(struct xt_xlate *xl);
void xt_xlate_add(struct xt_xlate *xl, const char *fmt, ...);
+void xt_xlate_add_comment(struct xt_xlate *xl, const char *comment);
const char *xt_xlate_get(struct xt_xlate *xl);
#ifdef XTABLES_INTERNAL
diff --git a/libxtables/xtables.c b/libxtables/xtables.c
index 32d6a5a..c4b86f5 100644
--- a/libxtables/xtables.c
+++ b/libxtables/xtables.c
@@ -1987,11 +1987,16 @@ void get_kernel_version(void)
kernel_version = LINUX_VERSION(x, y, z);
}
+#include <linux/netfilter/nf_tables.h>
+
struct xt_xlate {
- char *data;
- int size;
- int rem;
- int off;
+ struct {
+ char *data;
+ int size;
+ int rem;
+ int off;
+ } buf;
+ char comment[NFT_USERDATA_MAXLEN];
};
struct xt_xlate *xt_xlate_alloc(int size)
@@ -2002,20 +2007,20 @@ struct xt_xlate *xt_xlate_alloc(int size)
if (xl == NULL)
xtables_error(RESOURCE_PROBLEM, "OOM");
- xl->data = malloc(size);
- if (xl->data == NULL)
+ xl->buf.data = malloc(size);
+ if (xl->buf.data == NULL)
xtables_error(RESOURCE_PROBLEM, "OOM");
- xl->size = size;
- xl->rem = size;
- xl->off = 0;
+ xl->buf.size = size;
+ xl->buf.rem = size;
+ xl->buf.off = 0;
return xl;
}
void xt_xlate_free(struct xt_xlate *xl)
{
- free(xl->data);
+ free(xl->buf.data);
free(xl);
}
@@ -2025,16 +2030,22 @@ void xt_xlate_add(struct xt_xlate *xl, const char *fmt, ...)
int len;
va_start(ap, fmt);
- len = vsnprintf(xl->data + xl->off, xl->rem, fmt, ap);
- if (len < 0 || len >= xl->rem)
+ len = vsnprintf(xl->buf.data + xl->buf.off, xl->buf.rem, fmt, ap);
+ if (len < 0 || len >= xl->buf.rem)
xtables_error(RESOURCE_PROBLEM, "OOM");
va_end(ap);
- xl->rem -= len;
- xl->off += len;
+ xl->buf.rem -= len;
+ xl->buf.off += len;
+}
+
+void xt_xlate_add_comment(struct xt_xlate *xl, const char *comment)
+{
+ strncpy(xl->comment, comment, NFT_USERDATA_MAXLEN - 1);
+ xl->comment[NFT_USERDATA_MAXLEN - 1] = '\0';
}
const char *xt_xlate_get(struct xt_xlate *xl)
{
- return xl->data;
+ return xl->buf.data;
}
--
2.1.4
prev parent reply other threads:[~2016-02-01 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 18:43 [PATCH 1/3 iptables,xlate4] libxtables: fix leak in xt_buf object Pablo Neira Ayuso
2016-02-01 18:43 ` [PATCH 2/3 iptables,xlate4] extensions: rename xt_buf to xt_xlate Pablo Neira Ayuso
2016-02-01 18:43 ` Pablo Neira Ayuso [this message]
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=1454352216-18812-3-git-send-email-pablo@netfilter.org \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--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).