From: "Maciej Żenczykowski" <zenczykowski@gmail.com>
To: Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>,
Florian Westphal <fw@strlen.de>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: Android boot failure with 6.12
Date: Fri, 10 Jan 2025 14:23:22 -0800 [thread overview]
Message-ID: <CAHo-OozPA7Z9pwBgEA3whh_e3NBhVi1D7EC4EXjNJdVHYNToKg@mail.gmail.com> (raw)
In-Reply-To: <CAHo-OozVuh4wbTHLxM2Y2+qgQqHTwcmhAfeFOM9W8thqzz6gdg@mail.gmail.com>
Oh, wait
.family = NFPROTO_IPV4,
in the v6 section
On Fri, Jan 10, 2025 at 2:20 PM Maciej Żenczykowski
<zenczykowski@gmail.com> wrote:
>
> We've had to:
> Revert "netfilter: xtables: avoid NFPROTO_UNSPEC where needed"
> https://android-review.googlesource.com/c/kernel/common/+/3305935/2
>
> It seems the failure is (probably related to):
> ...
> E IptablesRestoreController: -A bw_INPUT -j MARK --or-mark 0x100000
> ...
> E IptablesRestoreController: ------- ERROR -------
> E IptablesRestoreController: Warning: Extension MARK revision 0 not
> supported, missing kernel module?
> E IptablesRestoreController: ip6tables-restore v1.8.10 (legacy): MARK
> target: kernel too old for --or-mark
> E IptablesRestoreController: Error occurred at line: 27
>
> But, I don't see an obvious bug in the CL we had to revert...
next prev parent reply other threads:[~2025-01-10 22:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 22:20 Android boot failure with 6.12 Maciej Żenczykowski
2025-01-10 22:23 ` Maciej Żenczykowski [this message]
2025-01-10 22:28 ` Maciej Żenczykowski
2025-01-10 22:36 ` Maciej Żenczykowski
2025-01-11 13:31 ` Jozsef Kadlecsik
2025-01-11 14:05 ` Florian Westphal
2025-01-11 16:51 ` Jozsef Kadlecsik
2025-01-11 14:17 ` Pablo Neira Ayuso
2025-01-11 16:53 ` Jozsef Kadlecsik
2025-01-11 13:57 ` 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=CAHo-OozPA7Z9pwBgEA3whh_e3NBhVi1D7EC4EXjNJdVHYNToKg@mail.gmail.com \
--to=zenczykowski@gmail.com \
--cc=fw@strlen.de \
--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;
as well as URLs for NNTP newsgroup(s).