public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug network/14498] New: default /var/db/services.db triggers infinite CPU loop with getaddrinfo()
Date: Mon, 20 Aug 2012 03:26:00 -0000	[thread overview]
Message-ID: <bug-14498-131@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 14498
           Summary: default /var/db/services.db triggers infinite CPU loop
                    with getaddrinfo()
           Product: glibc
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: network
        AssignedTo: unassigned@sourceware.org
        ReportedBy: vapier@gentoo.org
                CC: toolchain@gentoo.org
    Classification: Unclassified
              Host: x86_64-linux-gnu


using the default /var/db/Makefile provided by glibc:
cd /var/db
rm -f *.db
make

then running a simple getaddrinfo() request:
wget https://432020.bugs.gentoo.org/attachment.cgi?id=321736 -O test.c
gcc test.c
./a.out
<hang>

seems like we trigger an infinite cpu loop somewhere in the look up logic

(all details and example code provided by Maxim Kammerer)

reproduced with glibc-2.15 and 2.16

-- 
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.


             reply	other threads:[~2012-08-20  3:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20  3:26 vapier at gentoo dot org [this message]
2012-12-30 20:07 ` [Bug network/14498] " cloos at jhcloos dot com
2013-01-15 11:04 ` schwab@linux-m68k.org
2013-01-15 17:51 ` vapier at gentoo dot org
2013-01-15 18:36 ` vapier at gentoo dot org
2013-01-15 18:37 ` vapier at gentoo dot org
2013-01-15 18:38 ` vapier at gentoo dot org
2013-01-15 18:42 ` vapier at gentoo dot org
2014-06-25  6:49 ` fweimer at redhat dot com
2014-10-31  6:02 ` aoliva at sourceware dot org
2014-11-21  5:42 ` cvs-commit at gcc dot gnu.org
2014-11-21  6:27 ` 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-14498-131@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: 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).