From: Florian Westphal <fw@strlen.de>
To: Phil Sutter <phil@nwl.cc>,
"Remy D. Farley" <one-d-wide@protonmail.com>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org
Subject: Re: [PATCH] iptables: fix null dereference parsing bitwise operations
Date: Fri, 13 Feb 2026 14:17:19 +0100 [thread overview]
Message-ID: <aY8kXy5ZlvVIz1Ul@strlen.de> (raw)
In-Reply-To: <aY8hvMbo6JVX5hto@orbyte.nwl.cc>
Phil Sutter <phil@nwl.cc> wrote:
> > > '== NFT_BITWISE_MASK_XOR' and drop the comment.
> >
> >
> > It took me a while to realize iptables/linux headers are quite outdated,
> > so NFT_BITWISE_MASK_XOR is still called NFT_BITWISE_BOOL in there.
>
> Ah, sorry about that. I merely looked at current kernel headers to check
> if that magic zero could be replaced by something more descriptive.
Lets refresh the headers, then. == NFT_BITWISE_MASK_XOR would be
preferred.
prev parent reply other threads:[~2026-02-13 13:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 10:14 [PATCH] iptables: fix null dereference parsing bitwise operations Remy D. Farley
2026-02-11 21:36 ` Phil Sutter
2026-02-12 19:34 ` Remy D. Farley
2026-02-13 13:06 ` Phil Sutter
2026-02-13 13:17 ` Florian Westphal [this message]
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=aY8kXy5ZlvVIz1Ul@strlen.de \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=one-d-wide@protonmail.com \
--cc=pablo@netfilter.org \
--cc=phil@nwl.cc \
/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