Received-SPF: pass (google.com: domain of linux-kernel+bounces-187596-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH net v2] r8169: Fix possible ring buffer corruption on
 fragmented Tx packets.
From: patchwork-bot+netdevbpf@kernel.org
Message-Id: 
 <171647223337.20832.10658924978055829464.git-patchwork-notify@kernel.org>
Date: Thu, 23 May 2024 13:50:33 +0000
References: <27ead18b-c23d-4f49-a020-1fc482c5ac95@gmail.com>
In-Reply-To: <27ead18b-c23d-4f49-a020-1fc482c5ac95@gmail.com>
To: Ken Milmore <ken.milmore@gmail.com>
Cc: netdev@vger.kernel.org, hkallweit1@gmail.com, nic_swsd@realtek.com,
 edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
 linux-kernel@vger.kernel.org

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Tue, 21 May 2024 23:45:50 +0100 you wrote:
> An issue was found on the RTL8125b when transmitting small fragmented
> packets, whereby invalid entries were inserted into the transmit ring
> buffer, subsequently leading to calls to dma_unmap_single() with a null
> address.
> 
> This was caused by rtl8169_start_xmit() not noticing changes to nr_frags
> which may occur when small packets are padded (to work around hardware
> quirks) in rtl8169_tso_csum_v2().
> 
> [...]

Here is the summary with links:
  - [net,v2] r8169: Fix possible ring buffer corruption on fragmented Tx packets.
    https://git.kernel.org/netdev/net/c/c71e3a5cffd5

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