rpc.lockd(8) seg faults on 5.2-RELEASE

[Andrew P. Lentvorski, Jr.]

On Thu, 29 Jan 2004, Frode Nordahl wrote:

> Caught a new and different core dump from rpc.lockd today.
>
> (gdb) bt
> #0  dump_filelock (fl=0x809c000) at lockd_lock.c:318
> #1  0x0804e0a1 in lock_nfslock (fl=0x8080815) at lockd_lock.c:875

Your line numbering seems off.  You might want to provide a little more
context of what line actually failed.  ie. line 875 indicates a
test_nfslock() call and 318 is an initial function bracket

Nonetheless, the reasons for your core dumps elude me.  In both cases, the
fl should have caused a core dump *before* the line you are indicating.

-a