From: Pablo Neira Ayuso <pablo@netfilter.org>
To: netfilter-devel@vger.kernel.org
Subject: [PATCH nft] tests: py: fix incorrect bytecode in numgen and hash mappings
Date: Sat, 25 Feb 2017 12:43:15 +0100 [thread overview]
Message-ID: <1488022995-20560-1-git-send-email-pablo@netfilter.org> (raw)
Byteorder is not correct as it is expressed in network byteorder. This
uncovered when storing set byteorder in NFTA_USER_DATA.
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
---
tests/py/ip/hash.t.payload | 2 +-
tests/py/ip/numgen.t.payload | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/tests/py/ip/hash.t.payload b/tests/py/ip/hash.t.payload
index c410a8c67ef3..8c28ad98987e 100644
--- a/tests/py/ip/hash.t.payload
+++ b/tests/py/ip/hash.t.payload
@@ -29,7 +29,7 @@ ip test-ip4 pre
# dnat to jhash ip saddr mod 2 seed 0xdeadbeef map { 0 : 192.168.20.100, 1 : 192.168.30.100 }
__map%d test-ip4 b
__map%d test-ip4 0
- element 00000000 : 6414a8c0 0 [end] element 01000000 : 641ea8c0 0 [end]
+ element 00000000 : 6414a8c0 0 [end] element 00000001 : 641ea8c0 0 [end]
ip test-ip4 pre
[ payload load 4b @ network header + 12 => reg 2 ]
[ hash reg 1 = jhash(reg 2, 4, 0xdeadbeef) % mod 2 ]
diff --git a/tests/py/ip/numgen.t.payload b/tests/py/ip/numgen.t.payload
index a8ba21498795..04088b7562f3 100644
--- a/tests/py/ip/numgen.t.payload
+++ b/tests/py/ip/numgen.t.payload
@@ -6,7 +6,7 @@ ip test-ip4 pre
# dnat to numgen inc mod 2 map { 0 : 192.168.10.100, 1 : 192.168.20.200 }
__map%d x b
__map%d x 0
- element 00000000 : 640aa8c0 0 [end] element 01000000 : c814a8c0 0 [end]
+ element 00000000 : 640aa8c0 0 [end] element 00000001 : c814a8c0 0 [end]
ip test-ip4 pre
[ numgen reg 1 = inc mod 2 ]
[ lookup reg 1 set __map%d dreg 1 ]
--
2.1.4
reply other threads:[~2017-02-25 11:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1488022995-20560-1-git-send-email-pablo@netfilter.org \
--to=pablo@netfilter.org \
--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).