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

From: Andrew P. Lentvorski, Jr. <bsder_at_allcaps.org>
Date: Tue, 3 Feb 2004 14:12:01 -0800 (PST)

On Tue, 3 Feb 2004, Frode Nordahl wrote:

> Since it dies on bcmp, it seems like a null lock gets into the list for
> some reason.

Turn on the debug log and uncomment DUMP_FILELOCK_VERBOSE (or just the
filehandle dump code in dump_filelock).  One of those locks should have a
null pointer for the filehandle and that fact should be recorded in the
debug log.

-a

Received on Tue Feb 03 2004 - 13:04:32 UTC

This message: [ Message body ]
Next message: Tomas Verbaitis: "5.2.1-RC if_gre problems"
Previous message: Mark Koskenmaki: "Atheros support -ACK timing, etc"
In reply to: Frode Nordahl: "Re: rpc.lockd(8) seg faults on 5.2-RELEASE"
Next in thread: Frode Nordahl: "Re: rpc.lockd(8) seg faults on 5.2-RELEASE"
Reply: Frode Nordahl: "Re: rpc.lockd(8) seg faults on 5.2-RELEASE"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:41 UTC