Netdev List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Avi Weiss <thnkslprpt@gmail.com>
Cc: netdev@vger.kernel.org, akiyano@amazon.com, darinzon@amazon.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, evostrov@amazon.com
Subject: Re: [PATCH net v2 RESEND] net: ena: avoid double-counting TX DMA mappings on failure
Date: Wed, 18 Nov 2026 01:40:07 +0000	[thread overview]
Message-ID: <179496600727.1396957.5369288833503943166.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261115114233.2307630-2-thnkslprpt@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun, 15 Nov 2026 13:42:34 +0200 you wrote:
> ena_tx_map_skb() increments tx_info->num_of_bufs after each successful
> DMA mapping. If a later fragment mapping fails, the error path adds the
> fragment index to this count before calling ena_unmap_tx_buff(). This
> can cause DMA unmapping of buffers that were never mapped and
> out-of-bounds access to the buffer array.
> 
> Remove the extra increment so that cleanup uses only the number of
> successfully mapped buffers.
> 
> [...]

Here is the summary with links:
  - [net,v2,RESEND] net: ena: avoid double-counting TX DMA mappings on failure
    https://git.kernel.org/netdev/net/c/6e9764591bcc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-18  1:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15 11:42 [PATCH net v2 RESEND] net: ena: avoid double-counting TX DMA mappings on failure Avi Weiss
2026-11-17 11:50 ` Daniel Machon
2026-11-18  1:40 ` 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=179496600727.1396957.5369288833503943166.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=akiyano@amazon.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=darinzon@amazon.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=evostrov@amazon.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thnkslprpt@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