Re: URGENT: [diagnostic] cache_lock: blocked on 0xda5265a8 ""

[elekktretterr@xxxxxxxxxxxxxx]

if this bug is related to the cache_lock: blocked, it happens anytime
between 1-4 weeks. if this is something else, i dont know. ive seen it
happen occasionally on 1.8 but i never took a core dump. However, on 1.10
it has happened already the first day i put it on, even though NFS
actually wasnt mounted because i took the server home(this is an NFS
client, the NFS server is at work). The coredump youve seen is from 1.8, i
have made another one from 1.10.1 today. Dou you want to see it also?

I'll try the patch probably tomorrow when im on site.
Petr

>     Please try this patch and tell me if it works.  How many days does it
>     usually take for it to hit the bug?
>
> 						-Matt
>
>
> Index: kern/vfs_syscalls.c
> ===================================================================
> RCS file: /cvs/src/sys/kern/vfs_syscalls.c,v
> retrieving revision 1.112.2.1
> diff -u -p -r1.112.2.1 vfs_syscalls.c
> --- kern/vfs_syscalls.c	26 Jan 2007 18:55:31 -0000	1.112.2.1
> +++ kern/vfs_syscalls.c	30 Aug 2007 04:40:51 -0000
> @@ -2117,14 +2117,14 @@ 	 * If the file handle is stale we have
>  	 * is a hack at the moment.
>  	 */
>  	if (error == ESTALE) {
> +		vput(vp);
>  		cache_setunresolved(&nd->nl_nch);
>  		error = cache_resolve(&nd->nl_nch, nd->nl_cred);
> -		if (error == 0) {
> -			vput(vp);
> +		if (error == 0)
>  			goto again;
> -		}
> +	} else {
> +		vput(vp);
>  	}
> -	vput(vp);
>  	return (error);
>  }
>
>