From owner-freebsd-current@FreeBSD.ORG Fri May 30 02:04:14 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1762537B401 for ; Fri, 30 May 2003 02:04:14 -0700 (PDT) Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net [207.217.120.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8DE7043FA3 for ; Fri, 30 May 2003 02:04:13 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc0lu.dialup.mindspring.com ([209.86.2.190] helo=mindspring.com) by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19Lfo4-0001KL-00; Fri, 30 May 2003 02:04:12 -0700 Message-ID: <3ED71E39.A0F8EBC3@mindspring.com> Date: Fri, 30 May 2003 02:02:49 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bryan Liesner References: <20030529164240.X769@gravy.homeunix.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4bf3fbd90c71a0f161a103409cebe40b7350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: panic: kern/52718 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 May 2003 09:04:14 -0000 Bryan Liesner wrote: > > Is anyone going to look at this before the next release? > Of course, if more info is needed, I'll send it along. No dump is > available - it panics during boot. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=52718 This was caused by rev. 1.3 of a commit by Jeff Robertson to kern_utmx.c. The problem is that the proc struct is not locked for: FOREACH_THREAD_IN_PROC(td->td_proc, td0) in the lock and unlock. Either lock the proc before and unlock it after this, in both _utmx_lock() and _utmx_unlock(), or revert the code to 1.2. It's pretty simple. No one needs t look at it, all they need to do is act on information already present. -- Terry