[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173085783899.762099.17442482800210666704.git-patchwork-notify@kernel.org>
Date: Wed, 06 Nov 2024 01:50:38 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Aaron Conole <aconole@...hat.com>
Cc: netdev@...r.kernel.org, pshelar@....org, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com, horms@...nel.org,
dev@...nvswitch.org, linux-kernel@...r.kernel.org,
steffen.klassert@...unet.com, herbert@...dor.apana.org.au,
liuhangbin@...il.com
Subject: Re: [PATCH net-next] openvswitch: Pass on secpath details for internal
port rx.
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Fri, 1 Nov 2024 16:47:32 -0400 you wrote:
> Clearing the secpath for internal ports will cause packet drops when
> ipsec offload or early SW ipsec decrypt are used. Systems that rely
> on these will not be able to actually pass traffic via openvswitch.
>
> There is still an open issue for a flow miss packet - this is because
> we drop the extensions during upcall and there is no facility to
> restore such data (and it is non-trivial to add such functionality
> to the upcall interface). That means that when a flow miss occurs,
> there will still be packet drops. With this patch, when a flow is
> found then traffic which has an associated xfrm extension will
> properly flow.
>
> [...]
Here is the summary with links:
- [net-next] openvswitch: Pass on secpath details for internal port rx.
https://git.kernel.org/netdev/net-next/c/7d1c2d517f50
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists