From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: [musl] IPv4 fallback in __res_msend_rc not functional
Date: Fri, 26 Aug 2022 19:48:34 +0200 [thread overview]
Message-ID: <20220826174834.GD1923@voyager> (raw)
In-Reply-To: <20220826161603.GP7074@brightrain.aerifal.cx>
On Fri, Aug 26, 2022 at 12:16:03PM -0400, Rich Felker wrote:
> How does this look for handling the cases with no (usable)
> nameservers?
>
> diff --git a/src/network/res_msend.c b/src/network/res_msend.c
> index 105bf598..1e5f3516 100644
> --- a/src/network/res_msend.c
> +++ b/src/network/res_msend.c
> @@ -47,6 +47,11 @@ int __res_msend_rc(int nqueries, const unsigned char *const *queries,
> struct pollfd pfd;
> unsigned long t0, t1, t2;
>
> + if (!conf->nns) {
> + errno = ENOENT;
> + return -1;
> + }
> +
> pthread_setcancelstate(PTHREAD_CANCEL_DISABLE, &cs);
>
> timeout = 1000*conf->timeout;
> @@ -72,6 +77,11 @@ int __res_msend_rc(int nqueries, const unsigned char *const *queries,
>
> /* Handle case where system lacks IPv6 support */
> if (fd < 0 && family == AF_INET6 && errno == EAFNOSUPPORT) {
> + for (i=0; i<nns && conf->ns[nns].family == AF_INET6; i++);
> + if (i==nns) {
> + pthread_setcancelstate(cs, 0);
> + return -1;
> + }
> fd = socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0);
> family = AF_INET;
> sl = sizeof sa.sin;
>
> __res_msend returning -1 will cause getaddrinfo to fail with
> EAI_SYSTEM, in which case the caller can find the reason in errno.
>
> Rich
Seems like it would solve the problem. Except for the thing you already
mentioned.
Ciao,
Markus
prev parent reply other threads:[~2022-08-26 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 19:03 Markus Wichmann
2022-08-24 23:26 ` Rich Felker
2022-08-24 23:32 ` Rich Felker
2022-08-25 2:58 ` Markus Wichmann
2022-08-25 13:26 ` Rich Felker
2022-08-26 16:16 ` Rich Felker
2022-08-26 16:28 ` Rich Felker
2022-08-26 17:48 ` Markus Wichmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220826174834.GD1923@voyager \
--to=nullplan@gmx.net \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).