public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pablo at gnumonks dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/15015] getaddrinfo returns EAI_SERVICE with SOCK_RAW Date: Fri, 07 Feb 2014 09:55:00 -0000 [thread overview] Message-ID: <bug-15015-131-X874Bgi34J@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15015-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15015 --- Comment #5 from pablo at gnumonks dot org --- The question is, what's the reason for not allowing SOCK_RAW with getaddrinfo? The Linux kernel is providing that information via Netlink, so why should it artificially reject (through the GAI_PROTO_NOSERVICE flag) the request when it is indeed obtaining the information that we have requested? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-02-07 9:55 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-12 23:25 [Bug libc/15015] New: " pablo at gnumonks dot org 2013-01-12 23:29 ` [Bug libc/15015] " pablo at gnumonks dot org 2013-01-14 13:36 ` schwab@linux-m68k.org 2013-01-14 23:44 ` pablo at gnumonks dot org 2013-01-14 23:48 ` schwab@linux-m68k.org 2013-10-20 20:28 ` neleai at seznam dot cz 2014-02-07 2:52 ` [Bug network/15015] " jsm28 at gcc dot gnu.org 2014-02-07 9:55 ` pablo at gnumonks dot org [this message] 2014-02-13 15:59 ` asn at cryptomilk dot org 2014-02-13 16:00 ` asn at cryptomilk dot org 2014-06-13 19:04 ` fweimer at redhat dot com 2014-06-14 5:24 ` fweimer at redhat dot com 2014-09-27 6:28 ` aoliva at sourceware dot org
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-15015-131-X874Bgi34J@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: 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).