From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: "Krzysztof Olędzki" <ole@ans.pl>,
"Florian Westphal" <fw@strlen.de>,
"Pablo Neira Ayuso" <pablo@netfilter.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Ilya Katsnelson" <me@0upti.me>
Cc: stable@vger.kernel.org,
netfilter-devel <netfilter-devel@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: 6.6.57-stable regression: "netfilter: xtables: avoid NFPROTO_UNSPEC where needed" broke NFLOG on IPv6
Date: Sun, 20 Oct 2024 08:09:55 +0200 [thread overview]
Message-ID: <64702a91-e8c8-4d9e-92a0-e53c58e5ff77@leemhuis.info> (raw)
In-Reply-To: <8eb81c74-4311-4d87-9c13-be6a99c94e2f@ans.pl>
[CCing Ilya and the regression list, as it should be in the loop for
regressions: https://docs.kernel.org/admin-guide/reporting-regressions.html]
> Hi,
>
> After upgrading to 6.6.57 I noticed that my IPv6 firewall config failed to load.
>
> Quick investigation flagged NFLOG to be the issue:
>
> # ip6tables -I INPUT -j NFLOG
> Warning: Extension NFLOG revision 0 not supported, missing kernel module?
> ip6tables: No chain/target/match by that name.
>
> The regression is caused by the following commit:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/commit/?h=linux-6.6.y&id=997f67d813ce0cf5eb3cdb8f124da68141e91b6c
Not my area of expertise, but from a quick look is seems to be a known
problem due to some typos and people are working on a fix here:
https://lore.kernel.org/all/20241019-xtables-typos-v3-1-66dd2eaacf2f@0upti.me/
Ciao, Thorsten
> More precisely, the bug is in the change below:
>
> +#if IS_ENABLED(CONFIG_IP6_NF_IPTABLES)
> + {
> + .name = "NFLOG",
> + .revision = 0,
> + .family = NFPROTO_IPV4,
> + .checkentry = nflog_tg_check,
> + .destroy = nflog_tg_destroy,
> + .target = nflog_tg,
> + .targetsize = sizeof(struct xt_nflog_info),
> + .me = THIS_MODULE,
> + },
> +#endif
>
> Replacing NFPROTO_IPV4 with NFPROTO_IPV6 fixed the issue.
>
> Looking at the commit, it seems that at least one more target (MARK) may be also impacted:
>
> +#if IS_ENABLED(CONFIG_IP6_NF_IPTABLES)
> + {
> + .name = "MARK",
> + .revision = 2,
> + .family = NFPROTO_IPV4,
> + .target = mark_tg,
> + .targetsize = sizeof(struct xt_mark_tginfo2),
> + .me = THIS_MODULE,
> + },
> +#endif
>
> The same errors seem to be present in the main tree:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0bfcb7b71e735560077a42847f69597ec7dcc326
>
> I also suspect other -stable trees may be impacted by the same issue.
>
> Best regards,
> Krzysztof Olędzki
next prev parent reply other threads:[~2024-10-20 6:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-20 5:22 6.6.57-stable regression: "netfilter: xtables: avoid NFPROTO_UNSPEC where needed" broke NFLOG on IPv6 Krzysztof Olędzki
2024-10-20 6:09 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-10-20 12:51 ` Pablo Neira Ayuso
2024-10-21 2:57 ` Krzysztof Olędzki
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=64702a91-e8c8-4d9e-92a0-e53c58e5ff77@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=fw@strlen.de \
--cc=gregkh@linuxfoundation.org \
--cc=me@0upti.me \
--cc=netfilter-devel@vger.kernel.org \
--cc=ole@ans.pl \
--cc=pablo@netfilter.org \
--cc=regressions@lists.linux.dev \
--cc=stable@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