Subject: Re: nfs locking panic
To: Bill Sommerfeld <firstname.lastname@example.org>
From: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
Date: 11/18/1999 10:23:32
At 15:09 Uhr +0100 17.11.1999, Bill Sommerfeld wrote:
>knowing the value of p->p_locks and lockcount at this point will be
>useful (just to verify that something was left locked, as opposed to
>something extra being unlocked); also, in a DEBUG kernel, try calling
>printlockedvnodes() at this point..
A few printf()s later and with a -current kernel, I got
[hauke@elmo] ~ > ../../../../nfs/nfs_syscalls.c, line 618: p->p_locks = 1,
ount = 0 !
printlockedvnodes() says -266950656 ...
nfsd: locking botch in op 3
-- printlockedvnodes() may be bogus, I don't know what it returns (I used %d).
"It's never straight up and down" (DEVO)