summaryrefslogtreecommitdiff
path: root/src/thread/thrd_exit.c
diff options
context:
space:
mode:
authorRich Felker <dalias@aerifal.cx>2020-05-19 19:11:16 -0400
committerRich Felker <dalias@aerifal.cx>2020-05-19 19:11:16 -0400
commit5cf1ac2443ad0dba263559a3fe043d929e0e5c4c (patch)
tree38fc87c133680050def3847af545c466ec1987f1 /src/thread/thrd_exit.c
parentfd7ec068efd590c0393a612599a4fab9bb0a8633 (diff)
downloadmusl-5cf1ac2443ad0dba263559a3fe043d929e0e5c4c.tar.gz
musl-5cf1ac2443ad0dba263559a3fe043d929e0e5c4c.tar.bz2
musl-5cf1ac2443ad0dba263559a3fe043d929e0e5c4c.tar.xz
musl-5cf1ac2443ad0dba263559a3fe043d929e0e5c4c.zip
fix handling of errors resolving one of paired A+AAAA query
the old logic here likely dates back, at least in inspiration, to before it was recognized that transient errors must not be allowed to reflect the contents of successful results and must be reported to the application. here, the dns backend for getaddrinfo, when performing a paired query for v4 and v6 addresses, accepted results for one address family even if the other timed out. (the __res_msend backend does not propagate error rcodes back to the caller, but continues to retry until timeout, so other error conditions were not actually possible.) this patch moves the checks to take place before answer parsing, and performs them for each answer rather than only the answer to the first query. if nxdomain is seen it's assumed to apply to both queries since that's how dns semantics work.
Diffstat (limited to 'src/thread/thrd_exit.c')
0 files changed, 0 insertions, 0 deletions