mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ratheesh Kannoth <rkannoth@marvell.com>
To: Nicolai Buchwitz <nb@tipi-net.de>
Cc: Sunil Goutham <sgoutham@marvell.com>,
	Geetha sowjanya <gakula@marvell.com>,
	Subbaraya Sundeep <sbhatta@marvell.com>,
	Bharat Bhushan <bbhushan2@marvell.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	"Jakub Kicinski" <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, <netdev@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net 1/2] octeontx2-pf: fix skb use-after-free on ipsec transmit drop
Date: Wed, 28 Oct 2026 07:56:47 +0530	[thread overview]
Message-ID: <auFdZ-A2hKNWa7Wu@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <20261027-nb-otx2-ipsec-tx-fixes-net-v1-1-2114c4f10c36@tipi-net.de>

On 2026-10-28 at 01:24:06, Nicolai Buchwitz (nb@tipi-net.de) wrote:
> When an SA is removed while packets for it are still queued, the
> transmit path frees the packet but reports the queue as busy. The stack
> then requeues the freed skb, and the DMA mappings leak.
>
> Fixes: 6a77a158848a ("cn10k-ipsec: Process outbound ipsec crypto offload")
> Signed-off-by: Nicolai Buchwitz <nb@tipi-net.de>

Reviewed-by: Ratheesh Kannoth <rkannoth@marvell.com>

  reply	other threads:[~2026-10-28  2:27 UTC|newest]

Thread overview: 5+ 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 [this message]
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

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=auFdZ-A2hKNWa7Wu@rkannoth-OptiPlex-7090 \
    --to=rkannoth@marvell.com \
    --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=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

all inboxes | Powered by JetHome®