aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2020-06-24 21:51:03 -0700
committerDavid S. Miller <davem@davemloft.net>2020-06-24 21:51:03 -0700
commiteb2932b00fc75a154bb4607773dc0666924116ad (patch)
treee95e1549bb6733723ae5cdb2eb7f05fb04624762 /include
parentqed: add missing error test for DBG_STATUS_NO_MATCHING_FRAMING_MODE (diff)
parentnet: bcmgenet: use hardware padding of runt frames (diff)
downloadwireguard-linux-eb2932b00fc75a154bb4607773dc0666924116ad.tar.xz
wireguard-linux-eb2932b00fc75a154bb4607773dc0666924116ad.zip
Merge branch 'net-bcmgenet-use-hardware-padding-of-runt-frames'
Doug Berger says: ==================== net: bcmgenet: use hardware padding of runt frames Now that scatter-gather and tx-checksumming are enabled by default it revealed a packet corruption issue that can occur for very short fragmented packets. When padding these frames to the minimum length it is possible for the non-linear (fragment) data to be added to the end of the linear header in an SKB. Since the number of fragments is read before the padding and used afterward without reloading, the fragment that should have been consumed can be tacked on in place of part of the padding. The third commit in this set corrects this by removing the software padding and allowing the hardware to add the pad bytes if necessary. The first two commits resolve warnings observed by the kbuild test robot and are included here for simplicity of application. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions