This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
RE: [PATCH] posix/tst-getaddrinfo4: Consider EAI_NODATA as an expected result
- From: Alexey Brodkin <Alexey dot Brodkin at synopsys dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>, "linux-snps-arc at lists dot infradead dot org" <linux-snps-arc at lists dot infradead dot org>
- Date: Thu, 18 Apr 2019 16:58:38 +0000
- Subject: RE: [PATCH] posix/tst-getaddrinfo4: Consider EAI_NODATA as an expected result
- References: <20180730104036.4016-1-abrodkin@synopsys.com> <87v9zbwm7g.fsf@oldenburg2.str.redhat.com>
Hi Florian,
> -----Original Message-----
> From: Florian Weimer <fweimer@redhat.com>
> Sent: Thursday, April 18, 2019 3:08 PM
> To: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: libc-alpha@sourceware.org; linux-snps-arc@lists.infradead.org
> Subject: Re: [PATCH] posix/tst-getaddrinfo4: Consider EAI_NODATA as an expected result
>
> * Alexey Brodkin:
>
> > Some proxy DNS servers might not resolve IPv6 names to addresses.
> > Instead they reply with NOERROR while passing no real data.
> > That combination of NOERROR and EAI_NODATA happen because the DNS
> > server has a recored for requested name (example.net in our case)
> > but that record is not of AAAA type which was requested.
>
> I think this invalidates the test to a large degree. I don't think this
> is a valid test environment. You need to fix it.
I think more interesting would be to figure out if behavior that I see
is valid or not and then decide which test is representative.
>From my Googling I didn't find any data confirming that observed
behavior is incorrect, otherwise I would have asked our IT team to fix it.
Do you have a solid understanding that NOERROR && EIA_NODATA is not
valid combination?
-Alexey