summaryrefslogtreecommitdiffstats
path: root/lib
diff options
context:
space:
mode:
authorjmatthew <jmatthew@openbsd.org>2016-05-05 23:01:28 +0000
committerjmatthew <jmatthew@openbsd.org>2016-05-05 23:01:28 +0000
commit7edf5b0a3ee7fbef82e4e72869c50cbf1da9d652 (patch)
treed86340289e3bdbfdfbb55fdb93e08dfd2ca24cbf /lib
parentshow what we're doing when reordering libraries, otherwise the text (diff)
downloadwireguard-openbsd-7edf5b0a3ee7fbef82e4e72869c50cbf1da9d652.tar.xz
wireguard-openbsd-7edf5b0a3ee7fbef82e4e72869c50cbf1da9d652.zip
r1.10 of if_bnx.c effectively removed the limit on the number of segments in
the tx dma maps, apparently to allow heavily fragmented packets to be sent. The tx ring accounting in bnx_start assumed that the longest fragment chain we'd see was BNX_MAX_SEGMENTS, so sending a heavily fragmented packet when the ring was already full could cause it to overflow. In the 10 years since r1.10, we've started defragmenting packets if they won't fit in the dma map, so we can limit the maps to BNX_MAX_SEGMENTS again. While we're here, ensure there's always at least one slot on the tx ring free, for consistency between drivers. Fixes packet corruption seen by otto@ ok mpi@ dlg@
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions