From: Florian Westphal <fw@strlen.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, Zhiling Zou <zhilinz@nebusec.ai>
Subject: Re: [PATCH nf-next] netfilter: x_tables: reject missing '-p' flag and check for INV flag
Date: Mon, 24 Aug 2026 23:55:59 +0200 [thread overview]
Message-ID: <aoy977yxzSEsViun@strlen.de> (raw)
In-Reply-To: <aoy8kFZkXMNOHUcR@chamomile>
Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> > > Sashiko also hinting to fix ip6_tables core check for this protocol
> > > flag:
> > >
> > > https://sashiko.dev/#/patchset/20260821134136.18191-1-fw%40strlen.de
> >
> > Not so sure. Maybe just do this? I don't think proto > 0 and flag
> > unset makes any sense.
> >
> > diff --git a/net/ipv6/netfilter/ip6_tables.c b/net/ipv6/netfilter/ip6_tables.c
> > --- a/net/ipv6/netfilter/ip6_tables.c
> > +++ b/net/ipv6/netfilter/ip6_tables.c
> > @@ -647,6 +647,13 @@ check_entry_size_and_hooks(struct ip6t_entry *e,
> > /* Clear counters and comefrom */
> > e->counters = ((struct xt_counters) { 0, 0 });
> > e->comefrom = 0;
> > +
> > + /* Make sure F_PROTO is set, else ip6_packet_match
> > + * won't do the right thing.
> > + */
> > + if (e->ipv6.proto)
> > + e->ipv6.flags |= IP6T_F_PROTO;
>
> Userspace always provides a zeroed e->ipv6.proto when unused, correct?
Yes, ip6tables raises it when it parses '-p' option.
> If so, LGTM.
Alright, I will respin tomorrow, thanks.
Do you want me to include the TPROXY fix too?
next prev parent reply other threads:[~2026-08-24 21:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 13:41 [PATCH nf-next] netfilter: x_tables: reject missing '-p' flag and check for INV flag Florian Westphal
2026-08-21 14:02 ` Pablo Neira Ayuso
2026-08-22 8:14 ` Florian Westphal
2026-08-24 21:50 ` Pablo Neira Ayuso
2026-08-24 21:55 ` Florian Westphal [this message]
2026-08-24 22:18 ` Florian Westphal
2026-08-24 22:24 ` Pablo Neira Ayuso
2026-08-24 22:23 ` 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=aoy977yxzSEsViun@strlen.de \
--to=fw@strlen.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=zhilinz@nebusec.ai \
/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