Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 603
    • Issues 603
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • BINDBIND
  • Issues
  • #3132
Closed
Open
Issue created Feb 09, 2022 by Ondřej Surý@ondrejOwner

netmgr is missing TCP send timeout

When the uv_write() fills up the TCP send buffers (around 208k) on Linux because the other side is not reading, the TCP connection will be kept open indefinitely.

We need to add a "idle" timer around the uv_write(), so we can bail out early.

This also affects #1897 (closed) - the XFR timeout works fine, but the connection gets stuck as we have no way of terminating the pending uv_write()s on the stuck transfer.

FTR This is not CVE/ASN worthy because there's even a simpler way to keep the TCP connection open indefinitely - just keep sending and reading the DNS queries/responses, but keeping this confidential for the time being.

Assignee
Assign to
Time tracking