summaryrefslogtreecommitdiff
path: root/scripts/basic
diff options
context:
space:
mode:
authorPaolo Abeni <pabeni@redhat.com>2026-10-15 16:10:33 +0200
committerPaolo Abeni <pabeni@redhat.com>2026-10-15 16:10:33 +0200
commit36e6e826f7cd49f94e76fbfdc6f2873385c456d6 (patch)
tree198579d77dc7bd07b1b7eee7010d7e09aeed43d4 /scripts/basic
parent73022f605c447f31610b94ed4a983d2b4bf2c721 (diff)
parentb0f7f9c87817da1c72d093d3e5f249d45d8edf88 (diff)
Merge branch 'bnxt_en-fix-sw-uso-padding'
Joe Damato says: ==================== bnxt_en: Fix SW USO padding As a followup to Eric's fix a51d233ccd48 ("bnxt_en: fix DMA mapping length for padded small packets") which fixes padding for normal TX, this series fixes padding for SW USO. There are two cases I try to address: 1. The last segment could be shorter than BNXT_MIN_PKT_SIZE. So, add an extra BD if needed to pad to that minimum. 2. The gso_size is so small that every segment would be shorter than BNXT_MIN_PKT_SIZE (under 10 bytes with IPv4). This seems exceedingly unlikely, but just in case, it is handled by clearing the GSO features for these skbs so the stack segments them. Patch 1 is a small refactor to move code into a helper that patch 2 uses to avoid duplicating code. I ran v1 on a bnxt machine and re-ran the uso.py test and it passed, but the existing uso.py test doesn't test this specific case, so running the test was more of a regression test. There were no functional changes to v2. Note that I did not see this issue in production and it should not be possible for QUIC to hit this case on either ipv4 or ipv6 because QUIC packets are at least 21 bytes. AFAIU, only ipv4 segments with less than 10 bytes of UDP payload can trigger this. As such, I was asked to send this to net-next. v1: https://lore.kernel.org/netdev/20261008191114.3736826-1-joe@dama.to/ ==================== Link: https://patch.msgid.link/20261009215426.2377946-1-joe@dama.to Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'scripts/basic')
0 files changed, 0 insertions, 0 deletions