Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • HardenedBSD HardenedBSD
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 29
    • Issues 29
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • HardenedBSDHardenedBSD
  • HardenedBSDHardenedBSD
  • Repository
  • HardenedBSD
  • sys
  • netinet
  • tcp_stacks
  • rack.c
Find file BlameHistoryPermalink
  • Randall Stewart's avatar
    So it turns out that syzkaller hit another crash. It has to do with switching · 285385ba
    Randall Stewart authored Sep 09, 2020
    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.
    
    Sponsored by:	Netflix Inc.
    Differential Revision:	https://reviews.freebsd.org/D26269
    285385ba