From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
willemb@google.com
Subject: Re: [PATCH net-next v2 0/2] net: flow dissector: allow explicit passing of netns
Date: Thu, 27 Jun 2024 01:49:31 +0200 [thread overview]
Message-ID: <ZnypC7iOx_qtUH37@calendula> (raw)
In-Reply-To: <20240608221057.16070-1-fw@strlen.de>
Hi,
This series got applied to net-next.
But I can trigger this splat via nftables/tests/shell in net.git (6.10-rc).
As well as in -stable 6.1.x:
Jun 26 02:19:26 curiosity kernel: [ 1211.840595] ------------[ cut here ]------------
Jun 26 02:19:26 curiosity kernel: [ 1211.840605] WARNING: CPU: 0 PID: 70274 at net/core/flow_dissector.c:1016 __skb_flow_dissect+0x107e/0x2860
[...]
Jun 26 02:19:26 curiosity kernel: [ 1211.841240] CPU: 0 PID: 70274 Comm: socat Not tainted 6.1.93+ #18
I think that turning this into DEBUG_NET_WARN_ON_ONCE as Willem
suggested provides a workaround for net.git until Florian's fixes in
net-next hit -stable.
Would you accept such a patch?
Thanks.
On Sun, Jun 09, 2024 at 12:10:38AM +0200, Florian Westphal wrote:
> Change since last version:
> fix kdoc comment warning reported by kbuild robot, no other changes,
> thus retaining RvB tags from Eric and Willem.
> v1: https://lore.kernel.org/netdev/20240607083205.3000-1-fw@strlen.de/
>
> Years ago flow dissector gained ability to delegate flow dissection
> to a bpf program, scoped per netns.
>
> The netns is derived from skb->dev, and if that is not available, from
> skb->sk. If neither is set, we hit a (benign) WARN_ON_ONCE().
>
> This WARN_ON_ONCE can be triggered from netfilter.
> Known skb origins are nf_send_reset and ipv4 stack generated IGMP
> messages.
>
> Lets allow callers to pass the current netns explicitly and make
> nf_tables use those instead.
>
> This targets net-next instead of net because the WARN is benign and this
> is not a regression.
>
> Florian Westphal (2):
> net: add and use skb_get_hash_net
> net: add and use __skb_get_hash_symmetric_net
>
> include/linux/skbuff.h | 20 +++++++++++++++++---
> net/core/flow_dissector.c | 21 ++++++++++++++-------
> net/netfilter/nf_tables_trace.c | 2 +-
> net/netfilter/nft_hash.c | 3 ++-
> 4 files changed, 34 insertions(+), 12 deletions(-)
>
> --
> 2.44.2
>
next prev parent reply other threads:[~2024-06-26 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-08 22:10 [PATCH net-next v2 0/2] net: flow dissector: allow explicit passing of netns Florian Westphal
2024-06-08 22:10 ` [PATCH net-next v2 1/2] net: add and use skb_get_hash_net Florian Westphal
2024-06-08 22:10 ` [PATCH net-next v2 2/2] net: add and use __skb_get_hash_symmetric_net Florian Westphal
2024-06-09 5:06 ` [PATCH net-next v2 0/2] net: flow dissector: allow explicit passing of netns Eric Dumazet
2024-06-12 22:00 ` patchwork-bot+netdevbpf
2024-06-26 23:49 ` Pablo Neira Ayuso [this message]
2024-06-27 10:20 ` Paolo Abeni
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=ZnypC7iOx_qtUH37@calendula \
--to=pablo@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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