Page MenuHomeFreeBSD

tcp: Use local CC data only in correct context

Authored by rscheff on May 26 2021, 2:42 PM.



Many TCP CC mechanisms rely on newreno as fallback, or
to handle common behavior. Originally, cc_newreno did
not have any cc-specific data, but that changed with

Most other CC algos do use local data, and when calling
newreno_cong_signal from there, the latter misinterprets
the data as its own struct, leading to incorrect behavior.

Doing an additional check only in newreno for now, as
no other CC interdependencies seem to exist.

Test Plan

Using CC DCTCP on a session where ECN is not negotiated
would erroneously trigger session-specific beta values
on loss, leading to unexpected TCP behavior.

Reported by:

Diff Detail

rG FreeBSD src repository
Automatic diff as part of commit; lint not applicable.
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

Looks good to me. Thanks for picking this up! :)

This revision is now accepted and ready to land.May 26 2021, 2:58 PM