From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Maximets <i.maximets@ovn.org>
Cc: netdev@vger.kernel.org, aconole@redhat.com, echaudro@redhat.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, dev@openvswitch.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: openvswitch: fix skb leak on flow key update failure
Date: Thu, 30 Jul 2026 00:50:13 +0000 [thread overview]
Message-ID: <178537261363.3300615.16001981204180035474.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260727181851.306076-1-i.maximets@ovn.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 27 Jul 2026 20:18:29 +0200 you wrote:
> Fixes for two issues reported by Sashiko while reviewing other patches.
> The root cause is the same, fixes and the Fixes are slightly different,
> so two separate patches.
>
> Ilya Maximets (2):
> net: openvswitch: fix skb leak on flow key update failure during
> recirculation
> net: openvswitch: fix skb leak on flow key update failure during ct
>
> [...]
Here is the summary with links:
- [net,1/2] net: openvswitch: fix skb leak on flow key update failure during recirculation
https://git.kernel.org/netdev/net/c/e1cf066244da
- [net,2/2] net: openvswitch: fix skb leak on flow key update failure during ct
https://git.kernel.org/netdev/net/c/bc62e843bc48
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-07-30 0:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 18:18 [PATCH net 0/2] net: openvswitch: fix skb leak on flow key update failure Ilya Maximets
2026-07-27 18:18 ` [PATCH net 1/2] net: openvswitch: fix skb leak on flow key update failure during recirculation Ilya Maximets
2026-07-27 20:34 ` [net,1/2] " Aaron Conole
2026-07-27 18:18 ` [PATCH net 2/2] net: openvswitch: fix skb leak on flow key update failure during ct Ilya Maximets
2026-07-27 20:34 ` [net,2/2] " Aaron Conole
2026-07-30 0:50 ` 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=178537261363.3300615.16001981204180035474.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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