From: patchwork-bot+netdevbpf@kernel.org
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: davem@davemloft.net, kuba@kernel.org, gustavoars@kernel.org,
alobakin@pm.me, vladimir.oltean@nxp.com, edumazet@google.com,
paulb@nvidia.com, komachi.yoshiki@gmail.com, zhangkaiheb@126.com,
claudiajkang@gmail.com, ennoerlangen@gmail.com,
george.mccollister@gmail.com, bigeasy@linutronix.de,
netdev@vger.kernel.org, anthony.harivel@linutronix.de
Subject: Re: [PATCH net-next v1] flow_dissector: Add support for HSR
Date: Thu, 03 Mar 2022 07:00:11 +0000 [thread overview]
Message-ID: <164629081104.23910.1162758197965784868.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220228195856.88187-1-kurt@linutronix.de>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 28 Feb 2022 20:58:56 +0100 you wrote:
> Network drivers such as igb or igc call eth_get_headlen() to determine the
> header length for their to be constructed skbs in receive path.
>
> When running HSR on top of these drivers, it results in triggering BUG_ON() in
> skb_pull(). The reason is the skb headlen is not sufficient for HSR to work
> correctly. skb_pull() notices that.
>
> [...]
Here is the summary with links:
- [net-next,v1] flow_dissector: Add support for HSR
https://git.kernel.org/netdev/net-next/c/bf08824a0f47
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:[~2022-03-03 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 19:58 [PATCH net-next v1] flow_dissector: Add support for HSR Kurt Kanzenbach
2022-03-03 6:44 ` Jakub Kicinski
2022-03-03 8:08 ` Kurt Kanzenbach
2022-03-03 15:31 ` Jakub Kicinski
2022-03-03 15:48 ` Kurt Kanzenbach
2022-03-03 7:00 ` 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=164629081104.23910.1162758197965784868.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alobakin@pm.me \
--cc=anthony.harivel@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=claudiajkang@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=ennoerlangen@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=gustavoars@kernel.org \
--cc=komachi.yoshiki@gmail.com \
--cc=kuba@kernel.org \
--cc=kurt@linutronix.de \
--cc=netdev@vger.kernel.org \
--cc=paulb@nvidia.com \
--cc=vladimir.oltean@nxp.com \
--cc=zhangkaiheb@126.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).