Open Djfe opened 1 month ago
I forgot to mention @nbd168 (had to edit the post above)
This seems like an upstream issue? I can reproduce it with other linux distros as well
how did you reproduce it? Just by running iperf3 or a special command?
@Djfe see upstream https://github.com/esnet/iperf/issues/1694 https://github.com/esnet/iperf/issues/1692 https://github.com/esnet/iperf/issues/1681
It seems that the server crash because it receives "illegal" message from the client, and somehow it doesn't know to handle it well
I get this seg fault when i abruptly stop the client from performing the iperf test and then resuming with another client on the same port
@neheb x86_64 is little endian so that fix isn't applicable
It relates to JSON code.
Anyway, gdb is needed to figure this out.
Maintainer: @nbd168 Environment: x86_64, Hewlett-Packard HP EliteDesk 800 G1 USDT, OpenWrt GCC 12.3.0 r23899+10-3001d3c5d4 This was an OpenWrt fork: Gluon v2023.2.3 Which runs:
Description: I just noticed this segfault in dmesg after running a couple of iperf3 commands (I'm not sure which one triggered it or if it could've been triggered by a STRG+C by accident)