From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, sdf@google.com, dsahern@kernel.org,
idosch@nvidia.com
Subject: Re: [PATCH net] net: fib: avoid warn splat in flow dissector
Date: Thu, 31 Aug 2023 11:40:22 +0000 [thread overview]
Message-ID: <169348202260.28655.16047640718927905946.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230830110043.30497-1-fw@strlen.de>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 30 Aug 2023 13:00:37 +0200 you wrote:
> New skbs allocated via nf_send_reset() have skb->dev == NULL.
>
> fib*_rules_early_flow_dissect helpers already have a 'struct net'
> argument but its not passed down to the flow dissector core, which
> will then WARN as it can't derive a net namespace to use:
>
> WARNING: CPU: 0 PID: 0 at net/core/flow_dissector.c:1016 __skb_flow_dissect+0xa91/0x1cd0
> [..]
> ip_route_me_harder+0x143/0x330
> nf_send_reset+0x17c/0x2d0 [nf_reject_ipv4]
> nft_reject_inet_eval+0xa9/0xf2 [nft_reject_inet]
> nft_do_chain+0x198/0x5d0 [nf_tables]
> nft_do_chain_inet+0xa4/0x110 [nf_tables]
> nf_hook_slow+0x41/0xc0
> ip_local_deliver+0xce/0x110
> ..
>
> [...]
Here is the summary with links:
- [net] net: fib: avoid warn splat in flow dissector
https://git.kernel.org/netdev/net/c/8aae7625ff3f
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-08-31 11:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 11:00 [PATCH net] net: fib: avoid warn splat in flow dissector Florian Westphal
2023-08-30 14:46 ` Ido Schimmel
2023-08-30 14:56 ` David Ahern
2023-08-31 11:40 ` patchwork-bot+netdevbpf [this message]
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=169348202260.28655.16047640718927905946.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=dsahern@kernel.org \
--cc=fw@strlen.de \
--cc=idosch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@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;
as well as URLs for NNTP newsgroup(s).