Page MenuHomeFreeBSD

Another syzkaller crash
ClosedPublic

Authored by rrs on Sep 1 2020, 12:09 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 24 2024, 9:37 PM
Unknown Object (File)
Feb 6 2024, 12:34 PM
Unknown Object (File)
Jan 7 2024, 9:41 AM
Unknown Object (File)
Jan 2 2024, 6:00 PM
Unknown Object (File)
Dec 29 2023, 5:50 PM
Unknown Object (File)
Dec 20 2023, 6:13 AM
Unknown Object (File)
Dec 17 2023, 4:40 PM
Unknown Object (File)
Dec 13 2023, 3:47 AM
Subscribers

Details

Summary

So it turns out that syzkaller hit another crash. It has to do with switching
stacks with a SENT_FIN outstanding. Both rack and bbr will only send a
FIN if all data is ack'd so this must be enforced. Also if the previous stack
sent the FIN we need to make sure in rack that when we manufacture the
"unknown" sends that we include the proper HAS_FIN bits.

Note for BBR we take a simpler approach and just refuse to switch.

Test Plan

Run the syzkaller reproducer and verify that we no longer crash

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

rrs requested review of this revision.Sep 1 2020, 12:09 PM
rrs edited the summary of this revision. (Show Details)

Fix the typo's in the comment that Michael pointed out!

tuexen retitled this revision from Another skyzall crash to Another syzkaller crash.
tuexen edited the summary of this revision. (Show Details)
tuexen edited the test plan for this revision. (Show Details)

I ran the reproducers for RAVK and BBR and the problem does not show up anymore.

This revision is now accepted and ready to land.Sep 1 2020, 10:29 PM