Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 507
    • Issues 507
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 52
    • Merge requests 52
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #1148

Closed
Open
Created Mar 16, 2020 by Thomas Markwalder@tmarkMaintainer

dhcp_ddns::NameChangeSender send queue operations are not thread-safe

While working on a DDNS-related ticket it occurred to me that send queue operations in dhcp_ddns::NameChangeSender, which Kea-dhcpX servers use to talk to D2, are not thread-safe. NameChangeSender::send_queue_ is a std::deque<> instance. Each packet thread would be pushing NCRs onto the queue while the main thread is popping them off the front.

In the meantime, DDNS and MT, likely do not play well together.

Edited Mar 16, 2020 by Thomas Markwalder
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking