From owner-cvs-src@FreeBSD.ORG Thu Nov 10 06:41:46 2005 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74F8916A41F for ; Thu, 10 Nov 2005 06:41:46 +0000 (GMT) (envelope-from silby@silby.com) Received: from relay02.pair.com (relay02.pair.com [209.68.5.16]) by mx1.FreeBSD.org (Postfix) with SMTP id 677DB43D55 for ; Thu, 10 Nov 2005 06:41:45 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 24494 invoked from network); 10 Nov 2005 06:41:43 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 10 Nov 2005 06:41:43 -0000 X-pair-Authenticated: 209.68.2.70 Date: Thu, 10 Nov 2005 00:41:41 -0600 (CST) From: Mike Silbersack To: Doug White In-Reply-To: <200511092203.jA9M3omu013054@repoman.freebsd.org> Message-ID: <20051110004047.H10064@odysseus.silby.com> References: <200511092203.jA9M3omu013054@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern vfs_subr.c src/sys/fs/devfs devfs_vnops.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Nov 2005 06:41:46 -0000 On Wed, 9 Nov 2005, Doug White wrote: > dwhite 2005-11-09 22:03:50 UTC > > FreeBSD src repository > > Modified files: > sys/kern vfs_subr.c > sys/fs/devfs devfs_vnops.c > Log: > This is a workaround for a complicated issue involving VFS cookies and devfs. > The PR and patch have the details. The ultimate fix requires architectural > changes and clarifications to the VFS API, but this will prevent the system > from panicking when someone does "ls /dev" while running in a shell under the > linuxulator. > > This issue affects HEAD and RELENG_6 only. Oh, I wonder if this is why vmware3 on releng_6 panic'd my machine. I was in X, didn't get a backtrace, and assumed that something inside the vmware module was no longer functional. I shall have to test. Mike "Silby" Silbersack