From: patchwork-bot+netdevbpf@kernel.org
To: Rongzheng Wang <testwrzwrz@gmail.com>
Cc: netdev@vger.kernel.org, maciej.fijalkowski@intel.com,
magnus.karlsson@intel.com, kerneljasonxing@gmail.com,
sdf@fomichev.me, hawk@kernel.org, stable@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v5 0/2] xsk: fix multi-buffer TX software checksum
Date: Tue, 10 Nov 2026 11:20:06 +0000 [thread overview]
Message-ID: <179430960617.3882254.727568151015351636.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261104034809.24545-1-testwrzwrz@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 4 Nov 2026 11:48:07 +0800 you wrote:
> This is v5 of the AF_XDP multi-buffer TX software checksum fix.
>
> I found this while testing multi-buffer TX with XDP_UMEM_TX_SW_CSUM: a
> two-descriptor packet had a bad wire checksum, while a single descriptor
> was correct. There was no production or syzbot report.
>
> Patch 1 moves the software checksum calculation from xsk_skb_metadata() to
> the point where the last descriptor has been added to the skb. The old
> code calculated the checksum after the first descriptor, so multi-buffer
> packets only included the first fragment in the checksum.
>
> [...]
Here is the summary with links:
- [net,v5,1/2] xsk: defer software checksum until the skb is complete
https://git.kernel.org/netdev/net/c/f2eddafbfcc0
- [net,v5,2/2] selftests/bpf: cover AF_XDP multi-buffer TX software checksum
https://git.kernel.org/netdev/net/c/c112921763e7
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-11-10 11:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 3:48 Rongzheng Wang
2026-11-04 3:48 ` [PATCH net v5 1/2] xsk: defer software checksum until the skb is complete Rongzheng Wang
2026-11-04 3:48 ` [PATCH net v5 2/2] selftests/bpf: cover AF_XDP multi-buffer TX software checksum Rongzheng Wang
2026-11-10 11:20 ` 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=179430960617.3882254.727568151015351636.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=hawk@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--cc=stable@vger.kernel.org \
--cc=testwrzwrz@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
all inboxes | Powered by JetHome®