From owner-freebsd-stable@FreeBSD.ORG Wed Apr 9 11:29:18 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 78B9C37B408; Wed, 9 Apr 2003 11:29:18 -0700 (PDT) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4880F43FE9; Wed, 9 Apr 2003 11:29:17 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.12.9/8.12.8) with ESMTP id h39IT9MF048605; Wed, 9 Apr 2003 14:29:09 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.2.0.9.0.20030409142819.07c59c60@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca (Unverified) X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9 Date: Wed, 09 Apr 2003 14:35:12 -0400 To: Tor.Egge@cvsup.no.freebsd.org From: Mike Tancsa In-Reply-To: <20030409181835K.tegge@cvsup.no.freebsd.org> References: <5.2.0.9.0.20030409140404.07e83b18@marble.sentex.ca> <5.2.0.9.0.20030409121043.05c934a0@marble.sentex.ca> <5.2.0.9.0.20030409140404.07e83b18@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: By Sentex Communications (lava/20020517) cc: stable@freebsd.org Subject: Re: 3ware 3dmd broken in STABLE ( due to cvs commit: src/sys/kern kern_descrip.c kern_fork.c ) 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: Wed, 09 Apr 2003 18:29:18 -0000 At 06:18 PM 09/04/2003 +0000, Tor.Egge@cvsup.no.freebsd.org wrote: > > > > OK, some more information. As I narrowed it down to one day worth of > > commits, its easy enough to jump back and forth. Running ktrace -di > > /usr/local/sbin/3dmd shows its barfing when it goes to fork. > > > 199 3dmd CALL rfork(0x10) > > 199 3dmd RET rfork 200/0xc8 > >This explains the problem. The program calls rfork(RFPROC) which now >fails due to my commit to kern_fork.c. Reverting back to revision >1.72.2.11 of kern_fork.c should allow 3dmd to run, but it will also >allow for file lock leakage due to a shared file descriptor table >being used without a shared p_leader. Thanks. Is there a work around where the lock leakage can be fixed and the 3ware daemon can work ? I dont know who (if anyone) has the source code to the 3dmd program, is this something that could be easily fixed in it ? Are there any other programs that will break as a result of your commit as well ? ---Mike