dnstap: don't break request resolution on dnstap errors
This isn't a regression of 5.3.0 changes. Layer functions are supposed to return new values for ctx->state, but here we were sometimes returning kr_error(EFOO) which altered processing of the request. Our case: answers directly from policy module would not end up finishing the request and we'd hit an assert at the end of processing.
parent
4079a1a9
Branches
Tags v5.3.0
-
mentioned in commit 97b0c77f
-
mentioned in merge request !1151 (merged)
-
mentioned in commit e3e80088
Please register or sign in to comment