From rse@engelschall.com  Fri Jun 11 06:21:29 2004
Return-Path: <rse@engelschall.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5EABC16A4CE
	for <freebsd-gnats-submit@freebsd.org>; Fri, 11 Jun 2004 06:21:29 +0000 (GMT)
Received: from visp.engelschall.com (visp.engelschall.com [195.27.176.148])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A1C7943D41
	for <freebsd-gnats-submit@freebsd.org>; Fri, 11 Jun 2004 06:21:28 +0000 (GMT)
	(envelope-from rse@engelschall.com)
Received: by visp.engelschall.com (Postfix, from userid 1005)
	id 85FAD4CE535; Fri, 11 Jun 2004 08:21:32 +0200 (CEST)
Received: by en1.engelschall.com (Postfix, from userid 10000)
	id BAAE628611; Fri, 11 Jun 2004 08:21:02 +0200 (CEST)
Message-Id: <20040611062102.BAAE628611@en1.engelschall.com>
Date: Fri, 11 Jun 2004 08:21:02 +0200 (CEST)
From: Ralf S.Engelschall <rse@freebsd.org>
Reply-To: Ralf S.Engelschall <rse@freebsd.org>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: libc_r's resolver got broken between 2-Jun-2004 and 9-Jun-2004
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         67819
>Category:       kern
>Synopsis:       libc_r's resolver got broken between 2-Jun-2004 and 9-Jun-2004
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 11 06:30:08 GMT 2004
>Closed-Date:    Fri Jun 11 16:52:16 GMT 2004
>Last-Modified:  Fri Jun 11 16:52:16 GMT 2004
>Originator:     Ralf S. Engelschall
>Release:        FreeBSD 4.10-STABLE i386
>Organization:
Engelschall, Germany.
>Environment:
System: FreeBSD en1.engelschall.com 4.10-STABLE FreeBSD 4.10-STABLE #0: Wed Jun 9 09:38:39 CEST 2004 root@en1.engelschall.com:/v/dsk/0/g/usr.src/sys/compile/EN1 i386

>Description:
On 9-Jun-2004 I've upgraded my FreeBSD desktop at home to the latest
4.10-STABLE. After this Mozilla and Opera were no longer able to resolve
any DNS records. I've found that by just replacing /usr/lib/libc_r.so.4
with my backup copy from 4.10-STABLE as of 2-Jun-2004 the two
applications are running fine again. libc.so.4 seems to be not affected,
because only applications linked against libc_r.so.4 seemed to be
broken. So, some MFC to RELENG_4 between 2-Jun-2004 and 9-Jun-2004 has
broken the resolver in libc_r.

>How-To-Repeat:
Use latest 4.10-STABLE and try to run Opera 7.51 or Mozilla 1.6 and
watch them hanging forever displaying "Resolving www.example.com"
after entering http://www.example.com/.

>Fix:
I've not investigated what particular MFC between 2-Jun-2004 and
9-Jun-2004 caused this, but backing out this will certainly fix it
because using the libc_r.so.4 from 2-Jun-2004 fixes the problem
immediately. Sorry, I'm today leaving for holiday so I cannot
investigate myself further, but the problematic MFC should be not too
hard to find as there were not so much MFCs to libc during the mentioned
time range AFAIK.

>Release-Note:
>Audit-Trail:

From: Kris Kennaway <kris@obsecurity.org>
To: "Ralf S.Engelschall" <rse@FreeBSD.org>
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/67819: libc_r's resolver got broken between 2-Jun-2004 and 9-Jun-2004
Date: Fri, 11 Jun 2004 00:42:39 -0700

 On Fri, Jun 11, 2004 at 08:21:02AM +0200, Ralf S.Engelschall wrote:
 
 > >Fix:
 > I've not investigated what particular MFC between 2-Jun-2004 and
 > 9-Jun-2004 caused this, but backing out this will certainly fix it
 > because using the libc_r.so.4 from 2-Jun-2004 fixes the problem
 > immediately. Sorry, I'm today leaving for holiday so I cannot
 > investigate myself further, but the problematic MFC should be not too
 > hard to find as there were not so much MFCs to libc during the mentioned
 > time range AFAIK.
 
 Wasn't this already fixed?  Please cvsup again and confirm.
 
 Kris

From: "Ralf S. Engelschall" <rse@engelschall.com>
To: Kris Kennaway <kris@obsecurity.org>
Cc:  
Subject: Re: kern/67819: libc_r's resolver got broken between 2-Jun-2004 and 9-Jun-2004
Date: Fri, 11 Jun 2004 18:16:34 +0200

 On Fri, Jun 11, 2004, Kris Kennaway wrote:
 
 > On Fri, Jun 11, 2004 at 08:21:02AM +0200, Ralf S.Engelschall wrote:
 >
 > > >Fix:
 > > I've not investigated what particular MFC between 2-Jun-2004 and
 > > 9-Jun-2004 caused this, but backing out this will certainly fix it
 > > because using the libc_r.so.4 from 2-Jun-2004 fixes the problem
 > > immediately. Sorry, I'm today leaving for holiday so I cannot
 > > investigate myself further, but the problematic MFC should be not too
 > > hard to find as there were not so much MFCs to libc during the mentioned
 > > time range AFAIK.
 >
 > Wasn't this already fixed?  Please cvsup again and confirm.
 
 Yes, as of today (11-Jun-2004 12:00 CET) the RELENG_4 no longer
 shows this bug. Sorry, I was not aware that it was already fixed
 such fast. Thanks.
                                        Ralf S. Engelschall
                                        rse@engelschall.com
                                        www.engelschall.com
 
State-Changed-From-To: open->closed 
State-Changed-By: maxim 
State-Changed-When: Fri Jun 11 16:51:39 GMT 2004 
State-Changed-Why:  
MFC was reverted. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67819 
>Unformatted:
