From: Florian Westphal <fw@strlen.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
Eric Dumazet <edumazet@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jozsef Kadlecsik <kadlec@netfilter.org>
Subject: Re: [netfilter-core] [Q] The usage of xt_recseq.
Date: Wed, 14 Aug 2024 17:09:19 +0200 [thread overview]
Message-ID: <20240814150919.GA22825@breakpoint.cc> (raw)
In-Reply-To: <20240814071317.YbKDH7yA@linutronix.de>
Sebastian Andrzej Siewior <bigeasy@linutronix.de> wrote:
> On 2024-08-13 20:32:02 [+0200], Florian Westphal wrote:
> > Or, just tag the x_tables traversers as incompatible with
> > CONFIG_PREEMPT_RT in Kconfig...
>
> After reading all this I am kind of leaning in for the Kconfig option
> because it is legacy code. Do you have any schedule for removal?
No. I added a hidden kconfig symbol to allow for disabling it in
a9525c7f6219 ("netfilter: xtables: allow xtables-nft only builds")
I think we should wait a bit more before exposing the symbol
in Kconfig to reduce oldconfig breakage chances.
But I think all pieces are in place to allow for the removal.
next prev parent reply other threads:[~2024-08-14 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 14:01 [Q] The usage of xt_recseq Sebastian Andrzej Siewior
2024-08-13 14:37 ` [netfilter-core] " Florian Westphal
2024-08-13 15:28 ` Sebastian Andrzej Siewior
2024-08-13 18:32 ` Florian Westphal
2024-08-14 7:13 ` Sebastian Andrzej Siewior
2024-08-14 15:09 ` Florian Westphal [this message]
2024-08-14 15:22 ` Sebastian Andrzej Siewior
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=20240814150919.GA22825@breakpoint.cc \
--to=fw@strlen.de \
--cc=bigeasy@linutronix.de \
--cc=coreteam@netfilter.org \
--cc=edumazet@google.com \
--cc=kadlec@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.