public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kurt at roeckx dot be" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/15726] getaddrinfo() error codes
Date: Wed, 10 Jul 2013 21:35:00 -0000	[thread overview]
Message-ID: <bug-15726-131-9iaMd7ht4Z@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15726-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15726

--- Comment #2 from Kurt Roeckx <kurt at roeckx dot be> ---
(In reply to Andreas Schwab from comment #1)
> EAI_FAIL is only returned for an erroneous answer.  A negative answer is not
> erroneous.

I'm not sure what you're trying to say here.  I never said something about what
I think an erroneous answer should return.  But I can understand both EAI_FAIL
and EAI_AGAIN as valid return code for that case.

But that has nothing to do with what a negative answer should have as return
value.  And clearly EAI_NONAME is the wrong thing to return for any of the
cases I've mentioned that it currently returns it.

It should only return EAI_NONAME in case of:
- AI_NUMERICHOST was used and nodename is not a numeric string representing an
address.
- AI_NUMERICSERV was used and servname is not a numeric string representing a
port
- Both nodename and servname are NULL

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-07-10 21:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-10 18:04 [Bug network/15726] New: " kurt at roeckx dot be
2013-07-10 21:15 ` [Bug network/15726] " schwab@linux-m68k.org
2013-07-10 21:35 ` kurt at roeckx dot be [this message]
2013-07-10 21:44 ` schwab@linux-m68k.org
2013-07-10 21:45 ` kurt at roeckx dot be
2013-07-11 10:04 ` [Bug network/15726] getaddrinfo() returns incorrect status jdthood at gmail dot com
2013-07-11 13:27 ` zackw at panix dot com
2013-07-11 13:37 ` jdthood at gmail dot com
2013-07-11 16:54 ` kurt at roeckx dot be
2013-07-12 10:03 ` jdthood at gmail dot com
2013-07-14 16:08 ` bugdal at aerifal dot cx
2013-07-18  7:05 ` carlos at redhat dot com
2013-07-18 14:58 ` bugdal at aerifal dot cx
2013-07-18 17:45 ` carlos at redhat dot com
2013-07-30  7:05 ` jdthood at gmail dot com
2013-07-30  7:16 ` siddhesh at redhat dot com
2013-07-30 12:07 ` bugdal at aerifal dot cx
2013-07-31  4:08 ` carlos at redhat dot com
2013-08-09 14:35 ` kurt at roeckx dot be
2013-08-09 16:05 ` carlos at redhat dot com
2013-08-13 15:38 ` kurt at roeckx dot be
2013-08-13 19:25 ` carlos at redhat dot com
2013-08-24 18:08 ` kurt at roeckx dot be
2013-08-28  4:53 ` carlos at redhat dot com
2013-08-28  9:04 ` bugdal at aerifal dot cx
2013-08-28 21:20 ` kurt at roeckx dot be
2013-08-30  1:10 ` bugdal at aerifal dot cx
2013-08-30  7:11 ` kurt at roeckx dot be
2013-09-01  0:46 ` jdthood at gmail dot com
2013-09-01  2:11 ` jdthood at gmail dot com
2014-03-20 16:51 ` jdthood at gmail dot com
2014-03-21 11:26 ` jdthood at gmail dot com
2014-06-13 13:24 ` fweimer at redhat dot com

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=bug-15726-131-9iaMd7ht4Z@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.org \
    /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).