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 <[EMAIL PROTECTED]>
> > 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
