mld_v2_dispatch_general_query() is used by mld_fasttimo_vnet() to send
a reply to the MLDv2 General Query. 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 MLD_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 mld_v2_dispatch_general_query() to send remaining packets, we queue new reply in the same mbuf queue. And when number of packets is bigger than MLD_MAX_RESPONSE_BURST, we get endless reply of MLDv2 reports. To fix this, add the check for remaining packets in the queue. PR: 204831 MFC after: 1 week Sponsored by: Yandex LLC
This commit is contained in:
parent
0ec5645cbe
commit
e9c29fe907
@ -2985,6 +2985,15 @@ mld_v2_dispatch_general_query(struct mld_ifsoftc *mli)
|
||||
KASSERT(mli->mli_version == MLD_VERSION_2,
|
||||
("%s: called when version %d", __func__, mli->mli_version));
|
||||
|
||||
/*
|
||||
* Check that there are some packets queued. If so, send them first.
|
||||
* For large number of groups the reply to general query can take
|
||||
* many packets, we should finish sending them before starting of
|
||||
* queuing the new reply.
|
||||
*/
|
||||
if (mbufq_len(&mli->mli_gq) != 0)
|
||||
goto send;
|
||||
|
||||
ifp = mli->mli_ifp;
|
||||
|
||||
IF_ADDR_RLOCK(ifp);
|
||||
@ -3020,6 +3029,7 @@ mld_v2_dispatch_general_query(struct mld_ifsoftc *mli)
|
||||
}
|
||||
IF_ADDR_RUNLOCK(ifp);
|
||||
|
||||
send:
|
||||
mld_dispatch_queue(&mli->mli_gq, MLD_MAX_RESPONSE_BURST);
|
||||
|
||||
/*
|
||||
|
Loading…
Reference in New Issue
Block a user