public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "karme at karme dot de" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug network/12994] getaddrinfo fails if response records returned in wrong order and one of them is server failure Date: Tue, 06 Nov 2012 11:49:00 -0000 [thread overview] Message-ID: <bug-12994-131-K6VcFq9UTo@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-12994-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=12994 --- Comment #5 from karme at karme dot de 2012-11-06 11:49:19 UTC --- I now believe packet re-ordering is not enough to reproduce the problem. I have written a small dns proxy for better testing. The simplest scenario to reproduce the problem is to drop all a record requests and just answer the aaaa request. Answer for getaddrinfo with hints.ai_family = AF_UNSPEC is then error: r=-2 Name or service not known. Traffic is like: 12.786202 127.0.0.1 -> 127.0.0.1 DNS 68 Standard query 0x9f5f A karme.de 12.786962 127.0.0.1 -> 127.0.0.1 DNS 68 Standard query 0x77c8 AAAA karme.de 14.896700 127.0.0.1 -> 127.0.0.1 DNS 119 Standard query response 0x77c8 17.788941 127.0.0.1 -> 127.0.0.1 DNS 68 Standard query 0x9f5f A karme.de 22.794223 127.0.0.1 -> 127.0.0.1 DNS 68 Standard query 0x9f5f A karme.de -- 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.
next prev parent reply other threads:[~2012-11-06 11:49 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-13 4:24 [Bug libc/12994] New: " jik at kamens dot us 2011-07-13 4:24 ` [Bug libc/12994] " jik at kamens dot us 2011-07-13 4:25 ` jik at kamens dot us 2011-07-14 0:50 ` ppluzhnikov at google dot com 2011-07-16 5:33 ` nick.jones@network-box.com 2011-12-10 8:32 ` oliverml1 at oli1170 dot net 2012-02-21 2:17 ` [Bug network/12994] " jsm28 at gcc dot gnu.org 2012-11-02 1:22 ` jrnieder at gmail dot com 2012-11-03 17:01 ` karme at karme dot de 2012-11-04 10:49 ` karme at karme dot de 2012-11-04 10:53 ` karme at karme dot de 2012-11-06 11:49 ` karme at karme dot de [this message] 2012-11-06 13:22 ` law at redhat dot com 2012-11-07 17:33 ` karme at karme dot de 2012-11-27 12:02 ` karme at karme dot de 2012-11-27 16:52 ` law at redhat dot com 2012-12-16 15:55 ` psimerda at redhat dot com 2014-04-16 7:34 ` siddhesh at redhat dot com 2014-04-16 9:11 ` siddhesh at redhat dot com 2014-04-30 6:38 ` siddhesh at redhat dot com 2014-06-27 12:55 ` 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-12994-131-K6VcFq9UTo@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.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: linkBe 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).