public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug network/17630] endless loop in getaddr_r Date: Mon, 15 Dec 2014 09:50:00 -0000 [thread overview] Message-ID: <bug-17630-131-qpro4b36i5@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17630-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17630 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |ASSIGNED Assignee|unassigned at sourceware dot org |fweimer at redhat dot com Flags| |security+ --- Comment #10 from Florian Weimer <fweimer at redhat dot com> --- I can reproduce this with this small test program, and “networks: files dns” in /etc/nsswitch.conf, using the name “4.0.41.198.in-addr.arpa.”. #include <netdb.h> #include <err.h> #include <stdio.h> int main(int argc, char **argv) { struct netent *ne = getnetbyname(argv[1]); if (ne == NULL) { errx(1, "getnetbyname(%s) failed", argv[1]); } printf("n_name: %s\n", ne->n_name); if (ne->n_aliases) { printf("n_aliases:\n"); for (char **p = ne->n_aliases; *p; ++p) { printf(" %s\n", *p); } } printf("n_addrtype: %d\n", ne->n_addrtype); printf("n_net: 0x%08x\n", ne->n_net); return 0; } -- You are receiving this mail because: You are on the CC list for the bug. >From glibc-bugs-return-26880-listarch-glibc-bugs=sources.redhat.com@sourceware.org Mon Dec 15 14:47:27 2014 Return-Path: <glibc-bugs-return-26880-listarch-glibc-bugs=sources.redhat.com@sourceware.org> Delivered-To: listarch-glibc-bugs@sources.redhat.com Received: (qmail 23741 invoked by alias); 15 Dec 2014 14:47:26 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: <glibc-bugs.sourceware.org> List-Subscribe: <mailto:glibc-bugs-subscribe@sourceware.org> List-Post: <mailto:glibc-bugs@sourceware.org> List-Help: <mailto:glibc-bugs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs> Sender: glibc-bugs-owner@sourceware.org Delivered-To: mailing list glibc-bugs@sourceware.org Received: (qmail 23712 invoked by uid 48); 15 Dec 2014 14:47:21 -0000 From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/17702] Support recursive dlopen. Date: Mon, 15 Dec 2014 14:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: dynamic-link X-Bugzilla-Version: 2.20 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: security- X-Bugzilla-Changed-Fields: Message-ID: <bug-17702-131-1BCqjaw4c0@http.sourceware.org/bugzilla/> In-Reply-To: <bug-17702-131@http.sourceware.org/bugzilla/> References: <bug-17702-131@http.sourceware.org/bugzilla/> 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: 2014-12/txt/msg00123.txt.bz2 Content-length: 765 https://sourceware.org/bugzilla/show_bug.cgi?id\x17702 --- Comment #2 from Carlos O'Donell <carlos at redhat dot com> --- (In reply to johnandsara2 from comment #1) > dlopen should only connect to a lib, not cause any "initializations" It does run code and it should. After the library is loaded and relocations resolved it runs initializer functions, constructors, and static data initializers, all of which are required to correctly access the data and or functions in the library. Similarly it may run finialization functions and destructors at unload time. Is there any particular standard interpretation or use case that you think needs a "connect but don't yet use" semantic? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-12-15 9:50 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-20 13:44 [Bug network/17630] New: " yashavanth.hsn at gmail dot com 2014-11-20 14:47 ` [Bug network/17630] " schwab@linux-m68k.org 2014-11-24 16:29 ` yashavanth.hsn at gmail dot com 2014-11-24 16:31 ` yashavanth.hsn at gmail dot com 2014-11-24 16:58 ` schwab@linux-m68k.org 2014-11-25 9:48 ` yashavanth.hsn at gmail dot com 2014-12-09 13:34 ` schwab@linux-m68k.org 2014-12-12 14:06 ` fweimer at redhat dot com 2014-12-15 9:26 ` yashavanth.hsn at gmail dot com 2014-12-15 9:34 ` schwab@linux-m68k.org 2014-12-15 9:50 ` fweimer at redhat dot com [this message] 2014-12-15 9:50 ` yashavanth.hsn at gmail dot com 2014-12-16 9:10 ` cvs-commit at gcc dot gnu.org 2014-12-16 9:11 ` fweimer at redhat dot com 2014-12-18 1:07 ` cvs-commit at gcc dot gnu.org 2014-12-18 6:17 ` [Bug network/17630] endless loop in getaddr_r (CVE-2014-9402) fweimer at redhat dot com 2015-01-14 12:19 ` cvs-commit at gcc dot gnu.org 2015-01-14 13:13 ` cvs-commit at gcc dot gnu.org 2015-01-16 16:59 ` cvs-commit at gcc dot gnu.org 2015-01-16 17:02 ` cvs-commit at gcc dot gnu.org 2015-01-16 17:03 ` cvs-commit at gcc dot gnu.org 2015-01-21 13:56 ` cvs-commit at gcc dot gnu.org 2015-01-29 18:50 ` cvs-commit at gcc dot gnu.org 2015-02-12 13:05 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:06 ` cvs-commit at gcc dot gnu.org 2015-02-23 14:23 ` cvs-commit at gcc dot gnu.org 2015-02-23 15:02 ` cvs-commit at gcc dot gnu.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-17630-131-qpro4b36i5@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).