Page MenuHomeFreeBSD

TCP RACK: remove code that cannot be reached
ClosedPublic

Authored by tuexen on Jan 3 2025, 1:53 PM.
Tags
None
Referenced Files
F161597660: D48301.diff
Sun, Jul 5, 5:36 AM
Unknown Object (File)
Sat, Jul 4, 6:45 AM
Unknown Object (File)
Fri, Jul 3, 11:08 PM
Unknown Object (File)
Fri, Jul 3, 7:32 AM
Unknown Object (File)
May 26 2026, 9:03 AM
Unknown Object (File)
May 22 2026, 5:04 AM
Unknown Object (File)
May 21 2026, 8:46 AM
Unknown Object (File)
May 7 2026, 3:05 PM

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

tuexen requested review of this revision.Jan 3 2025, 1:53 PM

Are you sure this condition cannot be reached?

I would suspect you can have available data and the pace_tmr_rxt can be up ...

In D48301#1101717, @rrs wrote:

Are you sure this condition cannot be reached?

I would suspect you can have available data and the pace_tmr_rxt can be up ...

The code I am removing would only call return, if rsm == NULL and tmr_up == PACE_TMR_RXT. This condition can not be true, since the condition before if (rsm == NULL) reads:

	if (((rsm == NULL) || (tp->t_state < TCPS_ESTABLISHED)) &&
	    (tmr_up == PACE_TMR_RXT)) {
		/* Should be an RXT */
		return;
	}

which means we would return from that condition and never reach the code I am removing.

This revision is now accepted and ready to land.Jan 4 2025, 1:09 PM
This revision was automatically updated to reflect the committed changes.