Package: iperf
Version: 2.0.10+dfsg1-1

iperf segfaults with long runs on 40Gb/s NICs.

iperf -c 192.168.121.2 -P10 -w 130k -t 3600
------------------------------------------------------------
Client connecting to 192.168.121.2, TCP port 5001
TCP window size: 254 KByte (WARNING: requested 127 KByte)
------------------------------------------------------------
[ 10] local 192.168.121.3 port 40756 connected with 192.168.121.2 port
5001
[ 12] local 192.168.121.3 port 40760 connected with 192.168.121.2 port
5001
[ 11] local 192.168.121.3 port 40758 connected with 192.168.121.2 port
5001
[ 8] local 192.168.121.3 port 40754 connected with 192.168.121.2 port 5001
[ 9] local 192.168.121.3 port 40752 connected with 192.168.121.2 port 5001
[ 7] local 192.168.121.3 port 40750 connected with 192.168.121.2 port 5001
[ 6] local 192.168.121.3 port 40746 connected with 192.168.121.2 port 5001
[ 5] local 192.168.121.3 port 40748 connected with 192.168.121.2 port 5001
[ 3] local 192.168.121.3 port 40744 connected with 192.168.121.2 port 5001
[ 4] local 192.168.121.3 port 40742 connected with 192.168.121.2 port 5001
Segmentation fault (core dumped)

function byte_snprintf() when calculating SUM, where SUM is in terabyte,
we go past the kLabel_Byte/kLabel_bit array limit (by increment of conv
past kConv_Giga) and this causes iperf to segfault because suffix is
pointing past the array bounds.

A fix for this issue is available in:
https://sourceforge.net/p/iperf2/code/ci/fce3254827eb05fee56aa6a2e9f0d69cbe599a69/

--
============================
Manoj Iyer
Ubuntu/Canonical
ARM Servers - Cloud
============================

Reply via email to