From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Andrew Paniakin <apanyaki@amazon.com>
Cc: stable@vger.kernel.org, luizcap@amazon.com, benh@amazon.com,
Florian Westphal <fw@strlen.de>,
Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
"David S. Miller" <davem@davemloft.net>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4.14] netfilter: nf_tables: fix register ordering
Date: Tue, 23 May 2023 10:45:26 +0200 [thread overview]
Message-ID: <ZGx9JsCjvoDNRTBy@calendula> (raw)
In-Reply-To: <20230523025941.1695616-1-apanyaki@amazon.com>
On Mon, May 22, 2023 at 07:59:41PM -0700, Andrew Paniakin wrote:
> From: Florian Westphal <fw@strlen.de>
>
> commit d209df3e7f7002d9099fdb0f6df0f972b4386a63 upstream
>
> [ We hit the trace described in commit message with the
> kselftest/nft_trans_stress.sh. This patch diverges from the upstream one
> since kernel 4.14 does not have following symbols:
> nft_chain_filter_init, nf_tables_flowtable_notifier ]
>
> We must register nfnetlink ops last, as that exposes nf_tables to
> userspace. Without this, we could theoretically get nfnetlink request
> before net->nft state has been initialized.
I have to send pending batch of updates for -stable 4.14.
I take this patch and I will pass it on -stable maintainers.
Thanks.
next prev parent reply other threads:[~2023-05-23 8:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 2:59 [PATCH 4.14] netfilter: nf_tables: fix register ordering Andrew Paniakin
2023-05-23 8:45 ` Pablo Neira Ayuso [this message]
2023-05-23 17:09 ` Andrew Paniakin
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=ZGx9JsCjvoDNRTBy@calendula \
--to=pablo@netfilter.org \
--cc=apanyaki@amazon.com \
--cc=benh@amazon.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=luizcap@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).