GitLab

Summary

After upgrading bind from 9.16.26 to 9.18.1, there was a problem occured when using nslookup.

BIND version used

BIND 9.18.1 (Stable Release)

Steps to reproduce

Execute the following command line：# nslookup server

What is the current bug behavior?

The output as follows:

../../../bind-9.18.1/lib/isc/netmgr/netmgr.c:1703: REQUIRE((((handle) != ((void *)0) && ((const isc__magic_t *)(handle))->magic == ((('N') << 24 | ('M') << 16 | ('H') << 8 | ('D')))) && __extension__ ({ __auto_type __atomic_load_ptr = (&(handle)->references); __typeof__ ((void)0, *__atomic_load_ptr) __atomic_load_tmp; __atomic_load (__atomic_load_ptr, &__atomic_load_tmp, (5)); __atomic_load_tmp; }) > 0)) failed, back trace
/usr/lib64/libisc-9.18.1.so(+0x34634)[0x7f4916027634]
/usr/lib64/libisc-9.18.1.so(isc_assertion_failed+0xa)[0x7f491602758a]
/usr/lib64/libisc-9.18.1.so(isc__nmhandle_attach+0x63)[0x7f4916011143]
nslookup(+0xe75a)[0x55f46465c75a]
nslookup(+0xf555)[0x55f46465d555]
nslookup(+0x1193b)[0x55f46465f93b]
/usr/lib64/libisc-9.18.1.so(isc__nm_async_readcb+0xad)[0x7f49160143ed]
/usr/lib64/libisc-9.18.1.so(isc__nm_readcb+0x9b)[0x7f491601451b]
/usr/lib64/libisc-9.18.1.so(+0x2fe28)[0x7f4916022e28]
/usr/lib64/libisc-9.18.1.so(isc__nm_udp_read_cb+0x46)[0x7f4916024616]
/usr/lib64/libuv.so.1(+0x1ef1b)[0x7f4915b2ff1b]
/usr/lib64/libuv.so.1(+0x22cbb)[0x7f4915b33cbb]
/usr/lib64/libuv.so.1(uv_run+0x114)[0x7f4915b20824]
/usr/lib64/libisc-9.18.1.so(+0x22c2a)[0x7f4916015c2a]
/usr/lib64/libisc-9.18.1.so(isc__trampoline_run+0x16)[0x7f491604dce6]
/lib64/libc.so.6(+0x8a282)[0x7f4915bcc282]
/lib64/libc.so.6(+0x10b9a0)[0x7f4915c4d9a0]
Aborted

What is the expected correct behavior?

Server:    127.0.0.1
Address 1: 127.0.0.1 localhost.localdomain

Relevant configuration files

The default config file is used without any modification.