From: patchwork-bot+netdevbpf@kernel.org
To: Yoshiki Komachi <komachi.yoshiki@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jiri@resnulli.us, pshelar@ovn.org,
netdev@vger.kernel.org, dev@openvswitch.org,
toshiaki.makita1@gmail.com
Subject: Re: [PATCH net] cls_flower: Fix inability to match GRE/IPIP packets
Date: Fri, 29 Oct 2021 13:10:06 +0000 [thread overview]
Message-ID: <163551300689.9482.6803667652504679288.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211029092141.6924-1-komachi.yoshiki@gmail.com>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 29 Oct 2021 09:21:41 +0000 you wrote:
> When a packet of a new flow arrives in openvswitch kernel module, it dissects
> the packet and passes the extracted flow key to ovs-vswtichd daemon. If hw-
> offload configuration is enabled, the daemon creates a new TC flower entry to
> bypass openvswitch kernel module for the flow (TC flower can also offload flows
> to NICs but this time that does not matter).
>
> In this processing flow, I found the following issue in cases of GRE/IPIP
> packets.
>
> [...]
Here is the summary with links:
- [net] cls_flower: Fix inability to match GRE/IPIP packets
https://git.kernel.org/netdev/net/c/6de6e46d27ef
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:[~2021-10-29 13:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-29 9:21 [PATCH net] cls_flower: Fix inability to match GRE/IPIP packets Yoshiki Komachi
2021-10-29 13:10 ` 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=163551300689.9482.6803667652504679288.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=komachi.yoshiki@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=toshiaki.makita1@gmail.com \
--cc=xiyou.wangcong@gmail.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).