From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 required=5.0 tests=MAILING_LIST_MULTI,
	RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,
	T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 12239 invoked from network); 17 Feb 2022 13:24:50 -0000
Received: from mother.openwall.net (195.42.179.200)
  by inbox.vuxu.org with ESMTPUTF8; 17 Feb 2022 13:24:50 -0000
Received: (qmail 17582 invoked by uid 550); 17 Feb 2022 13:24:48 -0000
Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:musl@lists.openwall.com>
List-Help: <mailto:musl-help@lists.openwall.com>
List-Unsubscribe: <mailto:musl-unsubscribe@lists.openwall.com>
List-Subscribe: <mailto:musl-subscribe@lists.openwall.com>
List-ID: <musl.lists.openwall.com>
Reply-To: musl@lists.openwall.com
Received: (qmail 17545 invoked from network); 17 Feb 2022 13:24:47 -0000
Date: Thu, 17 Feb 2022 08:24:34 -0500
From: Rich Felker <dalias@aerifal.cx>
To: Satadru Pramanik <satadru@gmail.com>
Cc: musl@lists.openwall.com
Message-ID: <20220217132434.GP7074@brightrain.aerifal.cx>
References: <20220215174420.GL7074@brightrain.aerifal.cx>
 <CAFrh3J9rsT0taq5OoF7gi_jy7JdTzPQcSymT4S5abWyn4qHH_g@mail.gmail.com>
 <20220216014153.GM7074@brightrain.aerifal.cx>
 <CAFrh3J9EfO3GLOvfNCSG7Ru=Q4goiVXXSO-vL83ukfH_3d1_tg@mail.gmail.com>
 <CAFrh3J8X=w8ag4ZzkVO=bxsEUqsem=7BWtmLFCjHLNpcoGXBzA@mail.gmail.com>
 <20220216213335.GO7074@brightrain.aerifal.cx>
 <CAFrh3J_7NP0z2eyusSOmMnKc-5o-PjXG-E3OmncUUYB951Fvfg@mail.gmail.com>
 <CAFrh3J81o_XaFK3d1o1eBfQVePyTnqH=FJkt-e_MXFpnrHQ3iw@mail.gmail.com>
 <CAFrh3J9MnUEPe8RMY=wcmrG_iVduSoWzw2HCNFYj5-R8QXPB0g@mail.gmail.com>
 <CAFrh3J-tsT=uftRao_0CjKg=7LhCjrxanEDBvB6LEPkK+bW8vA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAFrh3J-tsT=uftRao_0CjKg=7LhCjrxanEDBvB6LEPkK+bW8vA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [musl] Re: musl getaddr info breakage on older kernels

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.