first deadlock from comment 27 fixed/workedaround. Next deadlock is:
thread A is the same as comment 27, holding view->lock and waiting for the bucket lock in dns_resolver_shutdown. now, thread B calls dispatch->authvalidated->nsecvalidate->create_fetch->dns_resolver_createfetch->dns_resolver_createfetch3 which does: LOCK(&res->buckets[bucketnum].lock); then calls fctx_create->fcount_incr which does: LOCK(&fctx->res->lock); where fctx->res is the view. So again, deadlock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1710278 Title: [2.3a1] named stuck on reload, DNS broken To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1710278/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
