UPDATE, REBOOT, FSCK! (#2) (was Re: filesystem corruption with kernel built on Friday.)

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

    I believe I foudn the system corruption bug.  It was a wild pointer in
    the LOCKF code.  It makes a lot of sense because the two reports I have
    used lockf heavily.  I am fairly certain that this is it.

    Everyone should update your systems, build and install a new kernel,
    and to be safe reboot into single-user and fsck normally before 
    rebooting normally.

    And after that, I expect only gleaming reports of perfection :-)

    ( This is also a good lesson in how one can be thrown off the mark.  For
    a long time I thought it was still FP related... but it isn't this time )

						-Matt