cvs commit: src/sys/kern kern_lockf.c

Matthew Dillon dillon at
Tue May 11 07:59:53 PDT 2004

:Matt, lf_destroy_range called with accounting == 0 doesn't follow any
:pointer in the range, it just uses the values directly. This is not the
:bug which corrupts the memory.

    Noooooo.  Damn.  I thought I had it, but you are right.  That can't be

    I still believe that the issue is related to the lockf code, somewhere.
    It's the only thing that fits the reports.

    Maybe the problem is more indirect... the earlier bug I had fixed was
    the error return code from lf_setlock().... it was returning success
    even if it failed.  But the only way that could cause system corruption
    would be if it had an adverse effect on something like X, and I don't
    see how.

					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>

More information about the Commits mailing list