From: patchwork-bot+netdevbpf@kernel.org
To: Zhou@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Yun <yun.zhou@windriver.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, qingfang.deng@linux.dev
Subject: Re: [PATCH v4] flow_dissector: check device type before reading ETH_ADDRS
Date: Fri, 19 Jun 2026 01:20:17 +0000 [thread overview]
Message-ID: <178183201788.3150917.7342180302629791951.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260616123057.482154-1-yun.zhou@windriver.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 16 Jun 2026 20:30:57 +0800 you wrote:
> __skb_flow_dissect() unconditionally reads 12 bytes from eth_hdr(skb)
> when FLOW_DISSECTOR_KEY_ETH_ADDRS is requested. This assumes the skb
> has a valid Ethernet header at mac_header, which is not always the case.
>
> The problem can be triggered by:
> 1. Creating a TUN device in L3 mode (IFF_TUN, hard_header_len=0)
> 2. Attaching a multiq qdisc with a flower filter matching on eth_src
> 3. Sending a packet through AF_PACKET
>
> [...]
Here is the summary with links:
- [v4] flow_dissector: check device type before reading ETH_ADDRS
https://git.kernel.org/netdev/net/c/bf6e8af2c8be
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:[~2026-06-19 1:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 12:30 [PATCH v4] flow_dissector: check device type before reading ETH_ADDRS Yun Zhou
2026-06-19 1:20 ` 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=178183201788.3150917.7342180302629791951.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Zhou@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=qingfang.deng@linux.dev \
--cc=yun.zhou@windriver.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 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.