Fix TCP SACK block generation in the base stack
ClosedPublic
Actions

Authored by tuexen on Sep 3 2019, 8:29 PM.

Tags

None

Referenced Files

	Unknown Object (File)
	Fri, Nov 14, 7:59 AM

	Unknown Object (File)
	Wed, Nov 5, 3:49 AM

	Unknown Object (File)
	Thu, Oct 30, 4:23 PM

	Unknown Object (File)
	Thu, Oct 30, 3:30 PM

	Unknown Object (File)
	Thu, Oct 30, 4:37 AM

	Unknown Object (File)
	Thu, Oct 16, 7:32 PM

	Unknown Object (File)
	Thu, Oct 16, 7:31 PM

	Unknown Object (File)
	Thu, Oct 16, 7:31 PM

View All 74 Files

Subscribers

imp

Details

Reviewers

rrs
rscheff

Group Reviewers

transport

Commits

rS351801: Fix the SACK block generation in the base TCP stack by bringing it in

Summary

This fixes the SACK block generation in the base stack by bringing it in sync with the RACK stack.

Diff Detail

Repository

rS FreeBSD src repository - subversion

Lint

Lint Not Applicable

Unit

Tests Not Applicable

Event Timeline

tuexen created this revision.Sep 3 2019, 8:29 PM

Herald added a reviewer: transport. · View Herald TranscriptSep 3 2019, 8:30 PM

Herald added a subscriber: imp. · View Herald Transcript

Harbormaster completed remote builds in B26259: Diff 61621.Sep 3 2019, 8:30 PM

rrs accepted this revision.Sep 3 2019, 9:35 PM

This revision is now accepted and ready to land.Sep 3 2019, 9:35 PM

Closed by commit rS351801: Fix the SACK block generation in the base TCP stack by bringing it in (authored by tuexen). · Explain WhySep 4 2019, 4:38 AM

This revision was automatically updated to reflect the committed changes.

tuexen added a commit: rS351801: Fix the SACK block generation in the base TCP stack by bringing it in.

tuexen mentioned this in rS360282: Improve the TCP SACK generation by reporting DSACKs.Apr 24 2020, 9:30 PM

Revision Contents
Changeset List

Path

Size

head/

sys/

netinet/

tcp_input.c

31 lines

Diff 61637

View Options

head/sys/netinet/tcp_input.c

Fix TCP SACK block generation in the base stackClosedPublicActions