Commit 77dc0918 authored by Michał Kępień's avatar Michał Kępień Committed by Ondřej Surý

Make dnstap work reliably with netmgr

The introduction of netmgr doubled the number of threads from which
dnstap data may be logged: previously, it could only happen from within
taskmgr worker threads; with netmgr, it can happen both from taskmgr
worker threads and from network threads.  Since the argument passed to
fstrm_iothr_options_set_num_input_queues() was not updated to reflect
this change, some calls to fstrm_iothr_get_input_queue() can now return
NULL, effectively preventing some dnstap data from being logged.
Whether this bug is triggered or not depends on thread scheduling order
and packet distribution between network threads, but will almost
certainly be triggered on any recursive resolver sooner or later.  Fix
by requesting the correct number of dnstap input queues to be allocated.
parent 96959447
......@@ -3677,7 +3677,11 @@ configure_dnstap(const cfg_obj_t **maps, dns_view_t *view) {
fopt = fstrm_iothr_options_init();
fstrm_iothr_options_set_num_input_queues(fopt, named_g_cpus);
* Both network threads and worker threads may log dnstap data.
2 * named_g_cpus);
# Using "-n 1" allows GL #1795 to be reliably reproduced
-D dnstap-ns3 -X named.lock -m record,size,mctx -c named.conf -d 99 -g -U 4 -n 1
......@@ -413,6 +413,7 @@
./bin/tests/system/dnstap/README TXT.BRIEF 2019,2020
./bin/tests/system/dnstap/ SH 2015,2016,2017,2018,2019,2020
./bin/tests/system/dnstap/large-answer.fstrm X 2019,2020
./bin/tests/system/dnstap/ns3/named.args X 2020
./bin/tests/system/dnstap/ SH 2018,2019,2020
./bin/tests/system/dnstap/ SH 2015,2016,2017,2018,2019,2020
./bin/tests/system/dnstap/ PYTHON 2016,2017,2018,2019,2020
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment