From owner-freebsd-stable@FreeBSD.ORG Wed Jul 30 21:52:24 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6EEB37B401; Wed, 30 Jul 2003 21:52:24 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-63-207-60-135.dsl.lsan03.pacbell.net [63.207.60.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B4D243F85; Wed, 30 Jul 2003 21:52:24 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id A6AB966BE5; Wed, 30 Jul 2003 21:52:23 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 8FFEAD93; Wed, 30 Jul 2003 21:52:23 -0700 (PDT) Date: Wed, 30 Jul 2003 21:52:23 -0700 From: Kris Kennaway To: Scot Loach Message-ID: <20030731045223.GA35485@rot13.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: alfred@FreeBSD.org cc: "'freebsd-stable@freebsd.org'" Subject: Re: kernel panic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2003 04:52:25 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 30, 2003 at 06:41:03PM -0400, Scot Loach wrote: > Yesterday I had a kernel panic on a FreeBSD 4.7 system. Looking at the c= ore > dump, it was caused by a corrupted uidinfo pointer referenced by a tcp pc= b. > I searched through the archives and found an identical stack trace in this > message from 2000: >=20 > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=3D322837+0+archive/2000/free= bsd-s > table/20000625.freebsd-stable >=20 > This was apparently fixed by a patch discussed in this thread. >=20 > http://www.geocrawler.com/archives/3/171/2000/11/0/4718890/ >=20 > The patch was applied to version 1.66 and 1.67 of /sys/kern/kern_resource= .c >=20 > I browsed through the CVS for these changes, but found no evidence of them > ever being merged to RELENG_4. >=20 > This is a real memory corruption in the kernel. If these changes were ne= ver > merged, does anyone know wny? Can anyone suggest a course of action to > resolve this?=20 It looks like most of the content of those commits were 5.0 specific, but you'd have to ask the committer about strategies for merging the behaviour. Kris --NzB8fVQJ5HfG6fxh Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/KKCHWry0BWjoQKURAtIJAKCqOs8Knu5yaRmDy9u66miWFsucCQCeKkVk jCs7T26yluuJ9qbmPEcjr4s= =cIrq -----END PGP SIGNATURE----- --NzB8fVQJ5HfG6fxh--