Page MenuHomeFreeBSD

TCP complete end status work.
ClosedPublic

Authored by rrs on Sep 26 2022, 12:22 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Jan 24, 5:21 PM
Unknown Object (File)
Sat, Jan 18, 5:57 PM
Unknown Object (File)
Thu, Jan 16, 5:57 PM
Unknown Object (File)
Thu, Jan 9, 9:21 PM
Unknown Object (File)
Dec 24 2024, 12:38 PM
Unknown Object (File)
Dec 5 2024, 12:33 AM
Unknown Object (File)
Oct 22 2024, 5:47 AM
Unknown Object (File)
Oct 11 2024, 7:16 AM
Subscribers

Details

Summary

The ending of a connection can tell us a lot about what happened i.e. did
it fail to setup, did it timeout, was it a normal close. Often times this is
useful information to help analyze and debug issues. Rack has had
end status for some time but the base stack as not. Lets go a ahead
and add in the missing bits to populate the end status.

Test Plan

Just bring up a connection with BB logging on and validate that
the end status gets populated at the close of the connection. For
extra points you can try killing the connection (with packet drill)
and see the various types of closes.

Diff Detail

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