summaryrefslogtreecommitdiffstats
path: root/lib/libc/tests/stdio/printbasic_test.c
diff options
context:
space:
mode:
authorae <ae@FreeBSD.org>2015-12-08 07:43:12 +0000
committerae <ae@FreeBSD.org>2015-12-08 07:43:12 +0000
commit58974a9f1d6e1285884033deebac6f9ab99b4c06 (patch)
tree8912ec092feb2d8abc81c3f05302717e8c144512 /lib/libc/tests/stdio/printbasic_test.c
parent0f5a92c989e527a15042aa0cb356fd0cb1359152 (diff)
downloadFreeBSD-src-58974a9f1d6e1285884033deebac6f9ab99b4c06.zip
FreeBSD-src-58974a9f1d6e1285884033deebac6f9ab99b4c06.tar.gz
MFC r291579:
In the same way fix the problem described in r291578 for IGMPv3. In case when router has a lot of multicast groups, the reply can take several packets due to MTU limitation. Also we have a limit IGMP_MAX_RESPONSE_BURST == 4, that limits the number of packets we send in one shot. Then we recalculate the timer value and schedule the remaining packets for sending. The problem is that when we call igmp_v3_dispatch_general_query() to send remaining packets, we queue new reply in the same mbuf queue. And when number of packets is bigger than IGMP_MAX_RESPONSE_BURST, we get endless reply of IGMPv3 reports. To fix this, add the check for remaining packets in the queue.
Diffstat (limited to 'lib/libc/tests/stdio/printbasic_test.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud