Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
BIND
BIND
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 635
    • Issues 635
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 105
    • Merge Requests 105
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #2100

Closed
Open
Opened Aug 26, 2020 by Tomek Mrugalski@tomek🛰Owner

assert in process_fd in libisc

There's an issue reported on Ubuntu [1] that ISC DHCP aborts on assert. But bear with me before you yell "get off my lawn then!". The exact backtrace reported is in [1]. There apparently seems to be a race condition that after a while leads to an assert in sock->pending_send called in process_fd in libisc. This was reported to ISC as [2] and [3]. @tmark looked at the issue and found out that one way to solve the problem is to build libisc with threads disabled. However, Ubuntu folks decided to go another route. They developed a patch for this problem [5] and that fix has been confirmed to solving their specific problem.

I'm opening this ticket to make sure the BIND team is aware of this problem and its potential solution. To be clear, if you decide it's not worth fixing, we can live without that fine.

The original report and patch is for bind 9.11.16, but I just checked that the code where assert blows up seems to be the same in 9.11.22.

References:

  • [1] Ubuntu report (backtrace, patch and discussion): https://bugs.launchpad.net/dhcp/+bug/1872118
  • [2] DHCP report #1 for Ubuntu: dhcp#121
  • [3] DHCP report #2 for Ubuntu: dhcp#128
  • [4] DHCP report from Yocto users: https://gitlab.isc.org/isc-projects/dhcp/-/issues/110
  • [5] patch: https://bugs.launchpad.net/dhcp/+bug/1872118/comments/46
Edited Aug 26, 2020 by Tomek Mrugalski
Assignee
Assign to
BIND 9.17 Backburner
Milestone
BIND 9.17 Backburner
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/bind9#2100