diff options
| author | 2026-11-10 12:07:02 +0100 | |
|---|---|---|
| committer | 2026-11-10 12:07:03 +0100 | |
| commit | af6f95c3300e3d234c813b80f831dd7b80b3eaf2 (patch) | |
| tree | cc59f51adeca7a4361a2f7fba4870f6e15a8fc2f /tools/perf/tests/shell/test_stackcollapse_python.sh | |
| parent | inet: frags: bound the wmem charge of the socket completing a reassembly (diff) | |
| parent | selftests/bpf: cover AF_XDP multi-buffer TX software checksum (diff) | |
Merge branch 'xsk-fix-multi-buffer-tx-software-checksum'
Rongzheng Wang says:
====================
xsk: fix multi-buffer TX software checksum
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.
Patch 2 sends the packet using every descriptor count from 1 through
MAX_SKB_FRAGS + 1, and runs the existing metadata and checksum verification
for each case. The last case is the copy-mode frame limit documented in
af_xdp.rst.
The updated selftest passes in a local QEMU run.
v4: https://lore.kernel.org/all/20261030023248.78802-1-testwrzwrz@gmail.com/
v3: https://lore.kernel.org/all/20261028025026.11401-1-testwrzwrz@gmail.com/
v2: https://lore.kernel.org/all/20261024141157.59301-1-testwrzwrz@gmail.com/
v1: https://lore.kernel.org/all/20261024091256.17918-1-testwrzwrz@gmail.com/
====================
Link: https://patch.msgid.link/20261104034809.24545-1-testwrzwrz@gmail.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'tools/perf/tests/shell/test_stackcollapse_python.sh')
0 files changed, 0 insertions, 0 deletions
