From: patchwork-bot+netdevbpf@kernel.org
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: sgoutham@marvell.com, gakula@marvell.com, rkannoth@marvell.com,
sbhatta@marvell.com, bbhushan2@marvell.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 0/2] octeontx2-pf: fix ipsec transmit error paths
Date: Thu, 29 Oct 2026 10:50:05 +0000 [thread overview]
Message-ID: <179327100532.1753346.16642826109370857631.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261027-nb-otx2-ipsec-tx-fixes-net-v1-0-2114c4f10c36@tipi-net.de>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 27 Oct 2026 20:54:05 +0100 you wrote:
> Two pre-existing bugs in the ipsec transmit error paths, flagged by the
> clashiko review of my earlier ipsec fix for this driver [1].
>
> Both look like edge cases to me, but at least the path in patch 1 (an SA
> removed during rekey or teardown while packets are still queued) looks
> plausible to me. But don't take my word for it, I'm not an octeontx2 user.
>
> [...]
Here is the summary with links:
- [net,1/2] octeontx2-pf: fix skb use-after-free on ipsec transmit drop
https://git.kernel.org/netdev/net/c/14d01ff1a495
- [net,2/2] octeontx2-pf: pass the skb to otx2_dma_unmap_skb_frags()
https://git.kernel.org/netdev/net/c/92cb8653970e
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-10-29 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 19:54 [PATCH net 0/2] octeontx2-pf: fix ipsec transmit error paths Nicolai Buchwitz
2026-10-27 19:54 ` [PATCH net 1/2] octeontx2-pf: fix skb use-after-free on ipsec transmit drop Nicolai Buchwitz
2026-10-28 2:26 ` Ratheesh Kannoth
2026-10-27 19:54 ` [PATCH net 2/2] octeontx2-pf: pass the skb to otx2_dma_unmap_skb_frags() Nicolai Buchwitz
2026-10-28 2:38 ` Ratheesh Kannoth
2026-10-29 10: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=179327100532.1753346.16642826109370857631.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=gakula@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nb@tipi-net.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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