FFe: bind9 9.16.1 update

Bug #1868272 reported by Andreas Hasenack
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bind9 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Bind just released 9.16.1. Focal has 9.16.0. This release was expected and is considered important, as it's the first point release after a new major one, and we should have it in focal.

UPDATE: debian just updated to 9.16.1 in experimental, just the upstream code update, nothing else.

Release notes: https://downloads.isc.org/isc/bind9/9.16.1/RELEASE-NOTES-bind-9.16.1.html

More detailed notes: https://gitlab.isc.org/isc-projects/bind9/-/blob/v9_16/CHANGES (look in the 9.16.1 section)

The one change that is indeed a feature change, and not a bug fix, is mentioned in the release notes only:
"""
Feature Changes

    The system-provided POSIX Threads read-write lock implementation is now used by default instead of the native BIND 9 implementation. Please be aware that glibc versions 2.26 through 2.29 had a bug that could cause BIND 9 to deadlock. A fix was released in glibc 2.30, and most current Linux distributions have patched or updated glibc, with the notable exception of Ubuntu 18.04 (Bionic) which is a work in progress. If you are running on an affected operating system, compile BIND 9 with --disable-pthread-rwlock until a fixed version of glibc is available. [GL !3125]
"""

The linked upstream glibc bug[1] still affects[2] bionic, and bionic only. I prepared an SRU for it, but I'm out of my depth on that one. I basically grabbed the patch, test case, and confirmed the test case no longer locks up with the patch applied.

Focal doesn't have that bug, but it's still worth to call out this change. It's upstream's new default, so they must have good reasoning for it. I emailed[3] the bind-users@ mailing list asking if they have more details on what that change means, or why it was made.

We can always disable it, by passing --disable-pthread-rwlock, in which case this FFe won't be strictly necessary.

PPA with test packages (where I did *NOT* pass --disable-pthread-rwlock, i.e., it's using upstream's default): https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3984/

Bileto ticket with green tests (bar i386, known): https://bileto.ubuntu.com/#/ticket/3984

1. https://sourceware.org/bugzilla/show_bug.cgi?id=23844#c14
2. https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1864864
3. https://lists.isc.org/pipermail/bind-users/2020-March/102786.html

Related branches

description: updated
description: updated
description: updated
Revision history for this message
Stéphane Graber (stgraber) wrote :

FFe granted, this feels more like a bugfix than a feature to me.
So certainly fine to do for focal.

Changed in bind9 (Ubuntu):
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bind9 - 1:9.16.1-0ubuntu1

---------------
bind9 (1:9.16.1-0ubuntu1) focal; urgency=medium

  * New upstream release: 19.16.1 (LP: #1868272)
    - drop d/p/bind-v9.16.0-tcp_quota_fix.patch, fixed upstream
    - drop d/p/Fix-dns_client_addtrustedkey.patch, fixed upstream
  * d/rules: change deprecated --with-libjson-c configure argument to
    --with-json-c

 -- Andreas Hasenack <email address hidden> Tue, 24 Mar 2020 11:44:46 -0300

Changed in bind9 (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.