BIND 9.16.1 on CentOS 6

[Ondřej Surý]

Hi Anand,

yes, it is.  The broken code was introduced in the glibc 2.26, and generally
RedHat/CentOS/Fedora/Debian libc6 already has the required patches.

Ubuntu 18.04 (and derivatives) is the only major Linux distribution that
doesn’t have the patch yet.

Ondrej
--
Ondřej Surý
ondrej at isc.org

> On 18 Mar 2020, at 15:33, Anand Buddhdev <anandb at ripe.net> wrote:
> 
> Hi BIND developers,
> 
> The 9.16.1 release notes say:
> 
> "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."
> 
> CentOS 6 has an older glibc version, 2.12. Is it safe to compile BIND on
> CentOS 6 with the system read-write lock implementation?
> 
> Regards,
> Anand
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 963 bytes
Desc: Message signed with OpenPGP
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20200318/b22cb218/attachment.bin>