From: Rich Felker <dalias@aerifal.cx>
To: Satadru Pramanik <satadru@gmail.com>
Cc: musl@lists.openwall.com
Subject: Re: [musl] Re: musl getaddr info breakage on older kernels
Date: Thu, 17 Feb 2022 08:24:34 -0500 [thread overview]
Message-ID: <20220217132434.GP7074@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAFrh3J-tsT=uftRao_0CjKg=7LhCjrxanEDBvB6LEPkK+bW8vA@mail.gmail.com>
On Thu, Feb 17, 2022 at 08:17:36AM -0500, Satadru Pramanik wrote:
> Looks like reverting that commit works, but interestingly, only
> stochastically.
>
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> getaddrinfo: Try again
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> AF_INET6: 2607:f8b0:4006:81c::200e
> AF_INET: 142.250.80.46
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> AF_INET6: 2607:f8b0:4006:81c::200e
> AF_INET: 142.250.80.46
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> getaddrinfo: Try again
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> AF_INET6: 2607:f8b0:4006:81c::200e
> AF_INET: 142.250.80.46
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> AF_INET6: 2607:f8b0:4006:81c::200e
> AF_INET: 142.250.80.46
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> getaddrinfo: Try again
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> AF_INET6: 2607:f8b0:4006:81c::200e
> AF_INET: 142.250.80.46
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> getaddrinfo: Try again
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> getaddrinfo: Try again
> chronos@localhost
> /usr/local/tmp/crew/musl_getaddrinfo_test.20220217125953.dir $
> ../musl_getaddrinfo_test google.com
> AF_INET6: 2607:f8b0:4006:81c::200e
> AF_INET: 142.250.80.46
Can you tcpdump these again and see if there's network traffic when it
fails? This sounds more like the nameserver being unreliable.
next prev parent reply other threads:[~2022-02-17 13:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFrh3J9CK67S=Jn531zTK04QeR8yiZwro_ZThQD=3aUx5XghCA@mail.gmail.com>
2022-02-06 21:30 ` Rich Felker
2022-02-06 23:25 ` Satadru Pramanik
2022-02-06 23:44 ` Rich Felker
2022-02-07 1:29 ` Satadru Pramanik
2022-02-07 2:40 ` Rich Felker
2022-02-07 19:19 ` Satadru Pramanik
2022-02-07 21:02 ` Rich Felker
2022-02-14 17:24 ` Satadru Pramanik
2022-02-14 18:29 ` Rich Felker
2022-02-14 19:00 ` Satadru Pramanik
2022-02-14 22:00 ` Rich Felker
2022-02-15 16:59 ` Satadru Pramanik
2022-02-15 17:44 ` Rich Felker
2022-02-15 22:56 ` Satadru Pramanik
2022-02-16 1:41 ` Rich Felker
2022-02-16 18:37 ` Satadru Pramanik
2022-02-16 18:44 ` Satadru Pramanik
2022-02-16 21:33 ` Rich Felker
2022-02-16 21:53 ` Satadru Pramanik
2022-02-17 1:44 ` Satadru Pramanik
2022-02-17 4:14 ` Satadru Pramanik
2022-02-17 13:17 ` Satadru Pramanik
2022-02-17 13:24 ` Rich Felker [this message]
2022-02-17 13:30 ` Satadru Pramanik
2022-02-17 13:46 ` Rich Felker
2022-02-17 14:49 ` Satadru Pramanik
2022-02-17 15:53 ` Rich Felker
2022-02-17 16:05 ` Rich Felker
2022-02-17 16:36 ` Satadru Pramanik
2022-02-17 18:17 ` Rich Felker
2022-02-17 21:39 ` Satadru Pramanik
2022-02-17 21:42 ` Satadru Pramanik
[not found] ` <CAFrh3J9CBGagzmnn9E7W0H15iiOzZEtg4YKfJ1qRwCtrjnw6tA@mail.gmail.com>
2022-02-17 21:43 ` Fwd: " Satadru Pramanik
2022-02-17 22:48 ` Rich Felker
2022-02-18 1:25 ` Satadru Pramanik
2022-02-17 16:17 ` Satadru Pramanik
2022-02-07 5:35 ` Markus Wichmann
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=20220217132434.GP7074@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
--cc=satadru@gmail.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).