rpc.lockd brokenness (2)

[Rong-En Fan]

On 3/6/06, Jun Kuriyama <kuriyama at imgsrc.co.jp> wrote:
>
> I'm not yet received enough information to track rpc.lockd problem.
>
> As Kris posted before, here is a patch to backout my suspected
> commit.  If someone can easily reproduce this problem, please try with
> this patch on both of server/client side of rpc.lockd (I'm not sure
> which of server/client side this affects).
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/80389
> http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84953
>
> Any reports about this patch (OK or still problem) are welcome!

Hi,

Somehow I have problems with lockd after 3 boxes upgraded from
Feb's RELENG_6 to Apr 6's. One of them has problems with lockd.
For example, mutt and irssi will stuck in lockd (shown by
top). I tried to back out changes in revision 1.18 for lock_proc.c,
and do /etc/rc.d/nfslocking stop then a start. After backout it,
mutt and irssi work well. If I put 1.18 back, mutt and irssi will stuck
in lockd again.

Last month, I played with the test program/script in those two PRs,
found that revision 1.18 does not make any difference. I'm not 100%
sure the problem I encountered now is related to rev 1.18. But
it is a report that  backout 1.18 really helps.

For record, all my clients involved in this mail are running RELENG_6.
Server is RELENG_5 as of March 9. Only IPv4 here, no IPv6.

Regards,
Rong-En Fan