[Bug network/14498] default /var/db/services.db triggers infinite CPU loop with getaddrinfo()

["aoliva at sourceware dot org" <sourceware-bugzilla@sourceware.org>]

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

Alexandre Oliva <aoliva at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |ASSIGNED
                 CC|                            |aoliva at sourceware dot org
           Assignee|unassigned at sourceware dot org   |aoliva at sourceware dot org

--- Comment #7 from Alexandre Oliva <aoliva at sourceware dot org> ---
Created attachment 7872
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7872&action=edit
two patches in one, both fixing the problem

We use some code from nss_files in nss_db, and nss_files' code used “continue”
to skip a non-matching proto, but in nss_db this bypassed the code to advance
to the next entry.  Both changes individually fix the problem; I'm undecided as
to which one to go with, or maybe even go with both.  Thoughts?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
>From glibc-bugs-return-26498-listarch-glibc-bugs=sources.redhat.com@sourceware.org Fri Oct 31 07:14:04 2014
Return-Path: <glibc-bugs-return-26498-listarch-glibc-bugs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-glibc-bugs@sources.redhat.com
Received: (qmail 17902 invoked by alias); 31 Oct 2014 07:14:04 -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 17786 invoked by uid 48); 31 Oct 2014 07:13:58 -0000
From: "aoliva at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/16001] calls to getaddrinfo() leak memory.
Date: Fri, 31 Oct 2014 07:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: glibc
X-Bugzilla-Component: network
X-Bugzilla-Version: 2.18
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aoliva at sourceware dot org
X-Bugzilla-Status: RESOLVED
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-16001-131-iJeyf7aXcE@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-16001-131@http.sourceware.org/bugzilla/>
References: <bug-16001-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-10/txt/msg00134.txt.bz2
Content-length: 439

https://sourceware.org/bugzilla/show_bug.cgi?id\x16001

--- Comment #5 from Alexandre Oliva <aoliva at sourceware dot org> ---
If I were to do that, how would the testcase report the memory leak?  The bug
report doesn't say that, and I don't see anything in the testcase that covers
that either.

Could this possibly have been fixed by the patch for bug 16002?

--
You are receiving this mail because:
You are on the CC list for the bug.