Subject: Re: procfs broken on -current?
To: Andrew Doran <ad@NetBSD.org>
From: Kouichirou Hiratsuka <firstname.lastname@example.org>
Date: 02/12/2007 16:40:22
At Sun, 11 Feb 2007 17:19:14 +0000,
Andrew Doran wrote:
> On Sat, Feb 10, 2007 at 11:33:50PM +0900, Kouichirou Hiratsuka wrote:
> > After accessing /proc/curproc/file, the process is hung up.
> > Does anyone else seeing this?
> procfs_lookup() was leaking a reference to the process when called against
> curproc, so it would get stuck draining references and couldn't exit. This
> should be fixed now:
> spanners$ ls -la /proc/curproc/file
> -r-xr-xr-x 1 root wheel 23633 Feb 10 12:32 /proc/curproc/file
It works fine for me too.
However, I got a kernel panic with the following command.
% ls -la /proc/*/*
Mutex error: mutex_vector_enter: locking against myself
lock address : 0x00000000c0505e70
current cpu : 0
current lwp : 0x00000000cbc6f2e0
owner field : 0x00000000cbc6f2e0 wait/spin: 0/0
panic: lock error
Stopped in pid 120.1 (ls) at netbsd:cpu_Debugger+0x4: leave