From: Fernando Fernandez Mancera <fmancera@suse.de>
To: "Remy D. Farley" <one-d-wide@protonmail.com>
Cc: Florian Westphal <fw@strlen.de>,
"netfilter-devel@vger.kernel.org"
<netfilter-devel@vger.kernel.org>
Subject: Re: iptables: zero dereference parsing bitwise operations
Date: Tue, 14 Oct 2025 17:14:57 +0200 [thread overview]
Message-ID: <e914fab4-e65d-43d3-a99d-816e8dffd72b@suse.de> (raw)
In-Reply-To: <c0jUt9xXxfO6o8KmFHUCZKJYW1bArw2X3KSLyVn39yv9-LiFW46XF0vnsPVV-QXkempUYu7kwzNsmG9rHM-65QjnqZ-mdz94Es2EPKbjbHI=@protonmail.com>
On 10/13/25 1:43 PM, Remy D. Farley wrote:
> On Monday, October 13th, 2025 at 09:04, Fernando Fernandez Mancera <fmancera@suse.de> wrote:
>
>> Hi Remy, could you share the full output of:
>>
>> 'nft --debug=netlink list ruleset'
>>
>> This will allow me to understand what is the generated bytecode and an
>> easy way to reproduce this with libnftnl. I am happy to investigate/fix
>> this on the nft/libnftnl/kernel side :)
>
>
> Hi Fernando,
>
> Not sure if it worth investigating, but here you go.
>
>
I have reproduced this and confirmed that the right source register is
being set (NFT_REG_1) and that libnftnl is reporting it correctly. The
problem is on nft command line tool side.. I do not think it is worth
going deeper as it is probably related to nftables not being able to
delinearize this rule as it is not supported by nft itself.
next prev parent reply other threads:[~2025-10-14 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 21:16 iptables: zero dereference parsing bitwise operations Remy D. Farley
2025-10-11 13:58 ` Florian Westphal
2025-10-11 20:15 ` Remy D. Farley
2025-10-12 16:46 ` Florian Westphal
2025-10-13 9:04 ` Fernando Fernandez Mancera
2025-10-13 11:43 ` Remy D. Farley
2025-10-14 15:14 ` Fernando Fernandez Mancera [this message]
2025-10-14 15:29 ` Florian Westphal
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=e914fab4-e65d-43d3-a99d-816e8dffd72b@suse.de \
--to=fmancera@suse.de \
--cc=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=one-d-wide@protonmail.com \
/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).