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

[Frode Nordahl]

Hello,

This is not a sollution, but I have run with this workaround since 
friday without incident.

I think there are two problems:
  - freed items are sometimes not removed from the nfslocklist
  - first element in blockedlocklist sometimes get wrong, causing a 
infinite loop in retry_blockingfilelocklist()

Mvh,
Frode
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rpc.lockd.patch
Type: application/octet-stream
Size: 1130 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20040210/6106284f/rpc.lockd.obj
-------------- next part --------------

On Feb 6, 2004, at 08:21, Andrew P. Lentvorski, Jr. wrote:

> On Thu, 5 Feb 2004, Frode Nordahl wrote:
>
>> I also found this in send_granted(): lockd_lock.c:2161
>>
>>          debuglog("About to send granted on blocked lock\n");
>>          sleep(1);
>>          debuglog("Blowing off return send\n");
>>
>> Anyone know what sleep(1) is good for here?
>
> The sleep() statements near debuglog() stuff are to work around the 
> fact
> that syslog has bugs where it arbitrarily and randomly eats messages 
> when
> you start sending too much data at it too quickly.
>
> By slowing down the logging, all of the messages get recorded.
>
> -a
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe at freebsd.org"