Date: Thu, 2 Nov 2000 13:32:27 -0500 (EST) From: Andrew Gallatin <gallatin@cs.duke.edu> To: "Akinori MUSHA" <knu@idaemons.org> Cc: Marcel Moolenaar <marcel@FreeBSD.org>, current@FreeBSD.org, morganw@chemicals.tacorp.com, phk@FreeBSD.org Subject: Re: cvs commit: src/sys/compat/linux linux_stats.c Message-ID: <14849.45097.838507.171552@grasshopper.cs.duke.edu> In-Reply-To: <86vgu6b939.wl@daemon.local.idaemons.org> References: <200011020608.WAA56694@freefall.freebsd.org> <86vgu6b939.wl@daemon.local.idaemons.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <morganw@chemicals.tacorp.com> > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14849.45097.838507.171552>