From owner-freebsd-current Thu Nov 2 10:34:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A6BA037B479; Thu, 2 Nov 2000 10:34:45 -0800 (PST) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA23410; Thu, 2 Nov 2000 13:32:28 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eA2IWSb07449; Thu, 2 Nov 2000 13:32:28 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 2 Nov 2000 13:32:27 -0500 (EST) To: "Akinori MUSHA" Cc: Marcel Moolenaar , current@FreeBSD.org, morganw@chemicals.tacorp.com, phk@FreeBSD.org Subject: Re: cvs commit: src/sys/compat/linux linux_stats.c In-Reply-To: <86vgu6b939.wl@daemon.local.idaemons.org> References: <200011020608.WAA56694@freefall.freebsd.org> <86vgu6b939.wl@daemon.local.idaemons.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14849.45097.838507.171552@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Akinori MUSHA writes: > At Wed, 1 Nov 2000 22:08:26 -0800 (PST), > Marcel Moolenaar wrote: > > marcel 2000/11/01 22:08:26 PST > > > > Modified files: > > sys/compat/linux linux_stats.c > > Log: > > Fix linux_ustat syscall. We only have cdevs now, so looking > > for a block device isn't that useful anymore. > > > > Reported by: Wesley Morgan > > Submitted by: gallatin > > Acknowledged by: phk > > After this change, it panics when you perform stat against a linux > block device node. Actually, emulators/vmware2 port creates some > block device nodes in /compat/linux/dev, so all the vmware2 users > still have ones installed. And when they hit `ls /compat/linux/dev' > or `pkg_delete vmware-2.0.x.yyy', they will see their boxen panic. ;) > > I'm 100% sure this change caused the panic because the stack trace > showed it panicked at vfinddev() called from linux_ustat(). > Hmm.. I seem to remember seeing something similar yesterday when my alpha was booting a brand new kernel with a 2 day-old userland. It was crashing in vfinddev called out of savecore and dev_mkdb. Thanks, Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message