]> git.ipfire.org Git - thirdparty/bind9.git/commit
Added test for the fix
authorDiego Fronza <diego@isc.org>
Mon, 25 May 2020 18:03:32 +0000 (15:03 -0300)
committerOndřej Surý <ondrej@sury.org>
Wed, 1 Jul 2020 09:59:01 +0000 (11:59 +0200)
commit042e509753062e8e2d829304f9f57f4e67011cb8
tree8048104b2f1221b06d0c089ceb20f6b96e7d8068
parentbe6cc53ec27e4549bf166d2161bacce688151e79
Added test for the fix

This test ensures that named will correctly shutdown
when receiving multiple control connections after processing
of either "rncd stop" or "kill -SIGTERM" commands.

Before the fix, named was crashing due to a race condition happening
between two threads, one running shutdown logic in named/server.c
and other handling control logic in controlconf.c.

This test tries to reproduce the above scenario by issuing multiple
queries to a target named instance, issuing either rndc stop or kill
-SIGTERM command to the same named instance, then starting multiple rndc
status connections to ensure it is not crashing anymore.
13 files changed:
bin/tests/system/Makefile.am
bin/tests/system/conf.sh.common
bin/tests/system/shutdown/clean.sh [new file with mode: 0644]
bin/tests/system/shutdown/conftest.py [new file with mode: 0644]
bin/tests/system/shutdown/ns1/named.conf.in [new file with mode: 0644]
bin/tests/system/shutdown/ns1/root.db [new file with mode: 0644]
bin/tests/system/shutdown/ns2/named.conf.in [new file with mode: 0644]
bin/tests/system/shutdown/ns2/test.db [new file with mode: 0644]
bin/tests/system/shutdown/resolver/named.conf.in [new file with mode: 0644]
bin/tests/system/shutdown/resolver/root.db [new file with mode: 0644]
bin/tests/system/shutdown/setup.sh [new file with mode: 0644]
bin/tests/system/shutdown/tests-shutdown.py [new file with mode: 0755]
util/copyrights