From: patchwork-bot+netdevbpf@kernel.org
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
Subject: Re: [PATCH net v2] r8169: Fix possible ring buffer corruption on fragmented Tx packets.
Date: Thu, 23 May 2024 13:50:33 +0000 [thread overview]
Message-ID: <171647223337.20832.10658924978055829464.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <27ead18b-c23d-4f49-a020-1fc482c5ac95@gmail.com>
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
prev parent reply other threads:[~2024-05-23 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-21 22:45 [PATCH net v2] r8169: Fix possible ring buffer corruption on fragmented Tx packets Ken Milmore
2024-05-22 5:35 ` Heiner Kallweit
2024-05-23 13: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=171647223337.20832.10658924978055829464.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=ken.milmore@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--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