From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12725 invoked by alias); 18 Jul 2013 07:05:14 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 10294 invoked by uid 48); 18 Jul 2013 07:03:11 -0000 From: "carlos at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug network/15726] getaddrinfo() returns incorrect status Date: Thu, 18 Jul 2013 07:05:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: network X-Bugzilla-Version: 2.17 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-07/txt/msg00106.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=15726 Carlos O'Donell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos at redhat dot com --- Comment #13 from Carlos O'Donell --- (In reply to Rich Felker from comment #12) > Conceptually, this whole topic is very simple. getaddrinfo has two > "successful" result possibilities, 0 and EAI_NONAME. > > 0 means a successful query was performed and returned a result. > > EAI_NONAME means a successful query was performed and determined that the > queried name does not (by hostname lookup) or cannot (by virtue of being an > invalid ip string) exist. > > All other result codes indicate to the application that something went wrong > during the name resolving process, and that the result is indeterminate. What about EAI_NODATA which glibc still uses? It would seem that EAI_NODATA is more likely be returned in the current implementation than EAI_NONAME (which is mostly returned for the parameter errors discussed). -- You are receiving this mail because: You are on the CC list for the bug.