Page MenuHomeFreeBSD

address possible illegal SACK block after FIN when client keeps sending data
AbandonedPublic

Authored by rscheff on Feb 24 2019, 1:52 PM.
Tags
None
Referenced Files
Unknown Object (File)
Dec 20 2023, 7:28 AM
Unknown Object (File)
Aug 2 2023, 6:12 PM
Unknown Object (File)
Jul 15 2023, 10:11 PM
Unknown Object (File)
Jul 1 2023, 10:33 AM
Unknown Object (File)
May 21 2023, 8:58 PM
Unknown Object (File)
May 9 2023, 9:34 AM
Unknown Object (File)
Dec 21 2022, 2:38 AM
Unknown Object (File)
Dec 10 2022, 12:55 AM
Subscribers

Details

Reviewers
tuexen
Group Reviewers
transport
Summary

If the socket option SBS_CANTRCVMORE is set, TCP will discard the received data, but update rcv_nxt.
Futhermore, not adjusting the actually accepted length could lead to illegal SACK blocks.

However, the impact seems minor, as that socket flag is only set once a FIN is received, and data beyond FIN is not expected.

Logically, we are not accepting the data...

Diff Detail

Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 22690
Build 21790: arc lint + arc unit

Event Timeline

rscheff retitled this revision from don't update rcv_nxt if socket can not receive. to address possible illegal SACK block after FIN when client keeps sending data.Feb 24 2019, 2:06 PM
rscheff edited the summary of this revision. (Show Details)
rscheff set the repository for this revision to rS FreeBSD src repository - subversion.