public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Thorsten Kukuk <kukuk@suse.de>
To: Roland McGrath <roland@redhat.com>
Cc: libc-hacker@sources.redhat.com
Subject: Re: AI_V4MAPPED/AI_ALL
Date: Mon, 31 Mar 2003 09:46:00 -0000	[thread overview]
Message-ID: <20030331071836.GA5335@suse.de> (raw)
In-Reply-To: <200303302208.h2UM8Vq32648@magilla.sf.frob.com>

[-- Attachment #1: Type: text/plain, Size: 2211 bytes --]

On Sun, Mar 30, Roland McGrath wrote:

> > Ok, AI_V4MAPPED and AI_ALL are specified in POSIX, rfc2553 and
> > rfc3493. So I doubt that it will be changed in the near future
> > again, I think something specified in POSIX should be stable 
> > enought to include in glibc.
> 
> Agreed.  I'm not sure the RFCs always indicate a stable interface, but
> what's in 1003.1-2001 we definitely want to implement and these are there.
> 
> Can you add a test case that is broken by the current code and fixed by
> your patch?  We can add an xtests case that requires some particular DNS
> zone data to do the test.  At least for forward zone data, I can set up a
> glibc-test.gnu.org subdomain with test data if needed.

I can write a test on basis of my current test program for this.
All I need is a hostname with only one IPv4 address and one with
a IPv4 and a IPv6 address.

I can also add test cases for more flags, but than reverse lookup
must work, too.

> > I append a patch which adds both defines to resolv/netdb.h and
> > implements it in getaddrinfo(). (Looking at the ugly getaddrinfo
> > code, it seems we really need a new, clean implementation :( ).
> 
> Definitely true.  It was close to the top of my list before you fixed the
> AF_UNSPEC behavior.  I can probably find time before the next release to do
> the rewrite.  If you have any list of known issues with the current
> implementation (aside from its internal structure), and especially if we
> can soup up the tests to cover more details, that would be a help.

There is a new flag AI_NUMERICSERV which is not supported and it
seems to me that return codes are wrong in most cases, too.

The WIDE project seems to have some tests for getaddrinfo, too. But
they expect that you have an entry for localhost with "::1" and
"127.0.0.1" in /etc/hosts. But maybe we can change this and add
this tests, too?

  Thorsten

-- 
Thorsten Kukuk       http://www.suse.de/~kukuk/        kukuk@suse.de
SuSE Linux AG        Deutschherrnstr. 15-19        D-90429 Nuernberg
--------------------------------------------------------------------    
Key fingerprint = A368 676B 5E1B 3E46 CFCE  2D97 F8FD 4E23 56C6 FB4B

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]

  reply	other threads:[~2003-03-31  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-24 17:59 AI_V4MAPPED/AI_ALL Thorsten Kukuk
2003-03-30 20:11 ` AI_V4MAPPED/AI_ALL Ulrich Drepper
2003-03-30 22:08   ` AI_V4MAPPED/AI_ALL Thorsten Kukuk
2003-03-30 23:33     ` AI_V4MAPPED/AI_ALL Roland McGrath
2003-03-31  9:46       ` Thorsten Kukuk [this message]
2003-03-31 13:29         ` AI_V4MAPPED/AI_ALL Roland McGrath
2003-03-31 21:36           ` AI_V4MAPPED/AI_ALL Thorsten Kukuk

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=20030331071836.GA5335@suse.de \
    --to=kukuk@suse.de \
    --cc=libc-hacker@sources.redhat.com \
    --cc=roland@redhat.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).