From: Ian Pilcher <arequipeno@gmail.com>
To: pablo@netfilter.org
Cc: netfilter-devel@vger.kernel.org
Subject: [RFC PATCH 0/1] libnftnl: Incorrect res_id byte order?
Date: Tue, 18 Oct 2022 11:45:27 -0500 [thread overview]
Message-ID: <20221018164528.250049-1-arequipeno@gmail.com> (raw)
I am marking this as an RFC and including this cover letter, because
I'm not absolutely 100% sure that the current code is incorrect. (It
obviously works, or this would have come up before.)
AFAICT, the res_id of struct nfgenmsg is supposed to be in network byte
order, and that isn't happening on little endian systems.
nftnl_batch_begin() and nftnl_batch_end() both pass NFNL_SUBSYS_NFTABLES
(10) to __nftnl_nlmsg_build_hdr(), but without a call to htons(), the
message contains 2560 (when interpretted in network byte order).
Ian Pilcher (1):
libnftnl: Fix res_id byte order
src/common.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
base-commit: 461f36979f4ed2b6cc95f06cf5f9c3c84bdf9e70
--
2.37.3
next reply other threads:[~2022-10-18 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 16:45 Ian Pilcher [this message]
2022-10-18 16:45 ` [RFC PATCH 1/1] libnftnl: Fix res_id byte order Ian Pilcher
2022-10-19 6:44 ` Pablo Neira Ayuso
2022-10-20 15:05 ` Ian Pilcher
2022-10-21 9:28 ` Pablo Neira Ayuso
2022-10-25 10:37 ` Pablo Neira Ayuso
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=20221018164528.250049-1-arequipeno@gmail.com \
--to=arequipeno@gmail.com \
--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