public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "psimerda at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/14415] AI_V4MAPPED is useless with AI_UNSPEC but they're used together as defaults when hints=NULL
Date: Thu, 03 Jan 2013 14:54:00 -0000	[thread overview]
Message-ID: <bug-14415-131-XyGqt6B18t@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14415-131@http.sourceware.org/bugzilla/>

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

--- Comment #5 from Pavel Šimerda <psimerda at redhat dot com> 2013-01-03 14:53:57 UTC ---
Created attachment 6794
  --> http://sourceware.org/bugzilla/attachment.cgi?id=6794
getaddrinfo: use zero ai_flags by default

    According to POSIX1-2008, AI_V4MAPPED flag shall be ignored unless
ai_family
    equals AF_INET6. In the default hints, ai_family is AF_UNSPEC. Therefore
    AI_V4MAPPED is redundant.

    AI_ADDRCONFIG can potentially be beneficial to applications that use
    getaddrinfo() results to immediately call connect(), sendto() and
    similar functions to avoid querying redundant DNS records according
    to the current address configuration.

    Those applications will also need to specify ai_socktype and/or
    ai_protocol and therefore will not use hints=NULL. As AI_DEFAULT is not
    a part of the public API, such applications will not be able to use the
    default flags at all.

    Please note that POSIX1-2008 doesn't define any default flags at all.

    Resolves: #14415, #14965

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2013-01-03 14:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-28  9:39 [Bug network/14415] New: " psimerda at redhat dot com
2012-07-31 18:44 ` [Bug network/14415] " tore at fud dot no
2012-08-03  4:04 ` carlos_odonell at mentor dot com
2012-08-03  4:06 ` carlos_odonell at mentor dot com
2012-08-03 16:12 ` psimerda at redhat dot com
2012-09-22 15:45 ` psimerda at redhat dot com
2012-12-04  0:00 ` carlos at systemhalted dot org
2013-01-03 14:54 ` psimerda at redhat dot com [this message]
2013-02-24 22:12 ` psimerda at redhat dot com
2013-10-20 20:54 ` neleai at seznam dot cz
2014-06-17 18:51 ` 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-14415-131-XyGqt6B18t@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).