Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dnsdist: Proper HTTP response for timeouts over DoH #7927

Merged
merged 6 commits into from Jul 17, 2019

Conversation

rgacogne
Copy link
Member

Short description

Timeouts, actively discovered or not, were not properly handled for DoH queries.
This PR is based on top of #7917 so we can send a proper HTTP status code, it will need to be rebased.

Checklist

I have:

  • read the CONTRIBUTING.md document
  • compiled this code
  • tested this code
  • included documentation (including possible behaviour changes)
  • documented the code
  • added or modified regression test(s)
  • added or modified unit test(s)

@rgacogne
Copy link
Member Author

Fixed the use-after-free race reported by ASAN on Circle CI.

In rare cases, the responder thread might get a response _before_
the send() call of the DoH client thread has returned, resulting
in ASAN reporting a use-after-free since the response was written
into the now useless query object.
@rgacogne
Copy link
Member Author

rgacogne commented Jul 8, 2019

Rebased now that #7917 has been merged.

pdns/dnsdist.cc Show resolved Hide resolved
pdns/dnsdistdist/doh.cc Show resolved Hide resolved
pdns/dnsdist.cc Show resolved Hide resolved
@omoerbeek
Copy link
Member

I must say I don't grasp all of dnsdist yet, but this PR look ok (with the one comment on the nullptr case).

@rgacogne
Copy link
Member Author

Giving up on the LGTM check, it is simply taking too long.

@rgacogne rgacogne merged commit 1353ea2 into PowerDNS:master Jul 17, 2019
@rgacogne rgacogne deleted the dnsdist-doh-timeout branch July 17, 2019 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants