Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • X xcap-capability-linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • xcap
  • xcap-capability-linux
  • Repository
Switch branch/tag
  • xcap-capability-linux
  • net
  • ipv4
  • tcp_input.c
Find file BlameHistoryPermalink
  • Ilpo Järvinen's avatar
    [TCP]: Update comment of SACK block validator · 0e835331
    Ilpo Järvinen authored Oct 01, 2007
    
    
    Just came across what RFC2018 states about generation of valid
    SACK blocks in case of reneging. Alter comment a bit to point
    out clearly.
    
    IMHO, there isn't any reason to change code because the
    validation is there for a purpose (counters will inform user
    about decision TCP made if this case ever surfaces).
    
    Signed-off-by: default avatarIlpo Järvinen <ilpo.jarvinen@helsinki.fi>
    Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
    0e835331