From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: [libnftnl PATCH] rule: Don't append a newline when printing a rule
Date: Tue, 1 Oct 2024 19:45:22 +0200 [thread overview]
Message-ID: <20241001175034.14037-1-phil@nwl.cc> (raw)
Since commit c759027a526ac, printed rules may or may not end with a
newline depending on whether userdata was present or not. Deal with this
inconsistency by avoiding the trailing newline in all cases.
Fixes: c759027a526ac ("rule, set_elem: remove trailing \n in userdata snprintf")
Signed-off-by: Phil Sutter <phil@nwl.cc>
---
This supersedes the previous patch with subject: Partially revert "rule,
set_elem: remove trailing \n in userdata snprintf" by solving the
problem in the opposite direction. As correctly assessed by Pablo, this
way is consistent with other printers.
I tested the change with nftables and iptables testsuites. It breaks a
single test in the latter which compares full ruleset debug output
against a record. To fix that, one could just pass --ignore-blank-lines
parameter to the diff call.
---
src/rule.c | 10 ++++------
1 file changed, 4 insertions(+), 6 deletions(-)
diff --git a/src/rule.c b/src/rule.c
index 811d5a213f835..c22918a8f3527 100644
--- a/src/rule.c
+++ b/src/rule.c
@@ -573,23 +573,21 @@ static int nftnl_rule_snprintf_default(char *buf, size_t remain,
sep = " ";
}
- ret = snprintf(buf + offset, remain, "\n");
- SNPRINTF_BUFFER_SIZE(ret, remain, offset);
-
list_for_each_entry(expr, &r->expr_list, head) {
- ret = snprintf(buf + offset, remain, " [ %s ", expr->ops->name);
+ ret = snprintf(buf + offset, remain,
+ "\n [ %s ", expr->ops->name);
SNPRINTF_BUFFER_SIZE(ret, remain, offset);
ret = nftnl_expr_snprintf(buf + offset, remain, expr,
type, flags);
SNPRINTF_BUFFER_SIZE(ret, remain, offset);
- ret = snprintf(buf + offset, remain, "]\n");
+ ret = snprintf(buf + offset, remain, "]");
SNPRINTF_BUFFER_SIZE(ret, remain, offset);
}
if (r->user.len) {
- ret = snprintf(buf + offset, remain, " userdata = { ");
+ ret = snprintf(buf + offset, remain, "\n userdata = { ");
SNPRINTF_BUFFER_SIZE(ret, remain, offset);
for (i = 0; i < r->user.len; i++) {
--
2.43.0
next reply other threads:[~2024-10-01 17:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 17:45 Phil Sutter [this message]
2024-10-01 18:46 ` [libnftnl PATCH] rule: Don't append a newline when printing a rule Pablo Neira Ayuso
2024-10-01 19:49 ` Phil Sutter
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=20241001175034.14037-1-phil@nwl.cc \
--to=phil@nwl.cc \
--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).