From: Phil Sutter <phil@nwl.cc>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [libnftnl PATCH] Partially revert "rule, set_elem: remove trailing \n in userdata snprintf"
Date: Tue, 1 Oct 2024 14:39:52 +0200 [thread overview]
Message-ID: <ZvvtmN2QKwOfTNp5@orbyte.nwl.cc> (raw)
In-Reply-To: <ZvvbzkNjJeEY25Fv@calendula>
Hi Pablo,
On Tue, Oct 01, 2024 at 01:23:58PM +0200, Pablo Neira Ayuso wrote:
> On Tue, Oct 01, 2024 at 01:20:54PM +0200, Phil Sutter wrote:
> > This reverts the rule-facing part of commit
> > c759027a526ac09ce413dc88c308a4ed98b33416.
> >
> > It can't be right: Rules without userdata are printed with a trailing
> > newline, so this commit made behaviour inconsistent.
>
> Did you run tests/py with this? It is the primary user for this.
It doesn't cover this because there's no test containing a rule with a
comment. I just added a respective test, but only to notice it does not
matter because nft-test.py compares rules' payload individually per-rule
and thus does not care whether output has a trailing newline or not.
I noticed it when testing the iptables compat ext stuff. You can easily
reproduce it like so:
| # nft --check --debug=netlink 'table t { chain c { accept comment mycomment; accept; accept;};}'
| ip (null) (null) use 0
| ip t c
| [ immediate reg 0 accept ]
| userdata = { \x00\x0amycomment\x00 }
| ip t c
| [ immediate reg 0 accept ]
|
| ip t c
| [ immediate reg 0 accept ]
Note the missing empty line after the first rule.
Cheers, Phil
next prev parent reply other threads:[~2024-10-01 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 11:20 [libnftnl PATCH] Partially revert "rule, set_elem: remove trailing \n in userdata snprintf" Phil Sutter
2024-10-01 11:23 ` Pablo Neira Ayuso
2024-10-01 12:39 ` Phil Sutter [this message]
2024-10-01 12:47 ` Pablo Neira Ayuso
2024-10-01 14:05 ` 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=ZvvtmN2QKwOfTNp5@orbyte.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).