This bug was fixed in the package bind9 - 1:9.10.3.dfsg.P4-8ubuntu1.15 --------------- bind9 (1:9.10.3.dfsg.P4-8ubuntu1.15) xenial; urgency=medium
* d/p/ubuntu//lp-1833400*: fix race on shutdown (LP: #1833400) * d/p/fix-shutdown-race.diff: dig/host/nslookup could crash when interrupted close to a query timeout (LP: #1797926) -- Christian Ehrhardt <christian.ehrha...@canonical.com> Mon, 05 Aug 2019 07:30:49 +0200 ** Changed in: bind9 (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1797926 Title: host crashed with SIGABRT in isc_assertion_failed() Status in BIND: Fix Released Status in bind9 package in Ubuntu: Fix Released Status in bind9 source package in Xenial: Fix Released Status in bind9 source package in Bionic: Fix Released Bug description: [Impact] * If a tool using the routines defined in bin/dig/dighost.c is sent an interruption signal around the time a connection timeout is scheduled to fire, connect_timeout() may be executed after destroy_libs() detaches from the global task (setting 'global_task' to NULL), which results in a crash upon a UDP retry due to bringup_timer() attempting to create a timer with 'task' set to NULL. * Fix by preventing connect_timeout() from attempting a retry when shutdown is in progress. [Test Case] * That is the bad part of this SRU, there is no known testcase. If you look at https://errors.ubuntu.com/problem/aba9505d17ecd495c2e68014d087e0bcb70a7a68 it seems often enough, but no clear "do this to trigger" :-/ Just like the other fix we intend to group with (for xenial). Maybe more time in proposed to be a bit safer? [Regression Potential] * This is in bind and Ubuntu releases for quite a while so general confidence is high. I could think of issue if this - on the backport - works differently as it is using a global variable (urgs) to detect if a shutdown is in progress. But overall it should replace a hard crash with a softer early exit that seems ok. [Other Info] * There is a patch adding "sleep 10" to the code to force the bug, but then I'd not test the packages in proposed right :-/ I wake up the computer.Then It shows a blank black screen with a sidebar (favourite apps).I can't login. Then I suspend the computer again and wake up it.It shows a error reporting dialog ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: bind9-host 1:9.11.4+dfsg-3ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Mon Oct 15 23:48:32 2018 ExecutablePath: /usr/bin/host InstallationDate: Installed on 2018-10-10 (5 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) ProcCmdline: host -t soa local. ProcEnviron: PATH=(custom, no user) Signal: 6 SourcePackage: bind9 StacktraceTop: isc_assertion_failed () from /usr/lib/x86_64-linux-gnu/libisc.so.169 isc.timer_create () from /usr/lib/x86_64-linux-gnu/libisc.so.169 ?? () ?? () ?? () Title: host crashed with SIGABRT in isc_assertion_failed() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/bind/+bug/1797926/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp