Page MenuHomeFreeBSD

Sanity check of SACK holes on retransmissions
ClosedPublic

Authored by rscheff on Jun 2 2022, 4:55 PM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, May 29, 1:21 AM
Unknown Object (File)
May 27 2024, 6:50 AM
Unknown Object (File)
May 16 2024, 3:38 PM
Unknown Object (File)
May 6 2024, 4:35 AM
Unknown Object (File)
Apr 27 2024, 6:19 AM
Unknown Object (File)
Apr 27 2024, 6:05 AM
Unknown Object (File)
Apr 27 2024, 6:05 AM
Unknown Object (File)
Apr 27 2024, 6:04 AM

Details

Summary

Adding a few KASSERT() to validate sanity of sack holes, and bail out if sack hole is inconsistent to avoid panicing non-invariant builds.

Diff Detail

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

Event Timeline

sys/netinet/tcp_sack.c
968

Don't you need to use the SEQ macros for this?

sys/netinet/tcp_sack.c
976

Maybe print something in non-debug case?

sys/netinet/tcp_sack.c
976

When printing them using %d, don't some of them show up as negative numbers? Would %u make more sense?

  • use SEQ_LT / GEQ macros
  • add logging

Thanks. Commiting with 1 week MFC...

This revision was not accepted when it landed; it landed in state Needs Review.Jun 7 2022, 7:41 AM
This revision was automatically updated to reflect the committed changes.