From: Florian Westphal <fw@strlen.de>
To: <netdev@vger.kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
<netfilter-devel@vger.kernel.org>,
Florian Westphal <fw@strlen.de>
Subject: [PATCH net-next 0/1] netfilter fix for net-next
Date: Wed, 28 Sep 2022 13:39:07 +0200 [thread overview]
Message-ID: <20220928113908.4525-1-fw@strlen.de> (raw)
Hello,
This is a late bug fix for the *net-next* tree to make nftables
"fib" expression play nice with VRF devices.
This was broken since day 1 (v4.10) so I don't see a compelling reason
to push this via net at the last minute.
Please consider pulling this change from
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf-next.git
----------------------------------------------------------------
The following changes since commit b9a5cbf8ba24e88071a97a51a09ef5cdf0d1f6a1:
Merge branch 'sfc-tc-offload' (2022-09-28 09:43:22 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf-next.git master
for you to fetch changes up to 2a8a7c0eaa8747c16aa4a48d573aa920d5c00a5c:
netfilter: nft_fib: Fix for rpath check with VRF devices (2022-09-28 13:33:26 +0200)
----------------------------------------------------------------
Phil Sutter (1):
netfilter: nft_fib: Fix for rpath check with VRF devices
net/ipv4/netfilter/nft_fib_ipv4.c | 3 +++
net/ipv6/netfilter/nft_fib_ipv6.c | 6 +++++-
2 files changed, 8 insertions(+), 1 deletion(-)
next reply other threads:[~2022-09-28 11:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 11:39 Florian Westphal [this message]
2022-09-28 11:39 ` [PATCH 1/1] netfilter: nft_fib: Fix for rpath check with VRF devices Florian Westphal
2022-09-28 17:40 ` patchwork-bot+netdevbpf
2022-09-29 16:10 ` Guillaume Nault
2022-09-29 16:21 ` Florian Westphal
2022-09-29 17:54 ` David Ahern
2022-09-30 14:10 ` Guillaume Nault
2022-09-30 14:47 ` Florian Westphal
2022-09-30 15:08 ` Guillaume Nault
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=20220928113908.4525-1-fw@strlen.de \
--to=fw@strlen.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).