2008-01-14 20:29:03

by Benjamin Coddington

[permalink] [raw]
Subject: Re: Strange lockup during unmount in 2.6.22 - maybe rpciod deadlock?

Trond Myklebust wrote:
> That shouldn't be the case in standard 2.6.22 unless you've also applied
> the NFS_ALL patches. In that case, there is a fix (which has also been
> applied to mainline) in
>
> http://client.linux-nfs.org/Linux-2.6.x/2.6.23-rc1/linux-2.6.23-001-fix_rpciod_down_race.dif

That fixed the problem -- still, do we care if we call async in
gss_destroying_context? On umount the server drops out from under the
tasks..

Ben


2008-01-14 20:37:03

by Trond Myklebust

[permalink] [raw]
Subject: Re: Strange lockup during unmount in 2.6.22 - maybe rpciod deadlock?


On Mon, 2008-01-14 at 15:28 -0500, Benjamin Coddington wrote:
> Trond Myklebust wrote:
> > That shouldn't be the case in standard 2.6.22 unless you've also applied
> > the NFS_ALL patches. In that case, there is a fix (which has also been
> > applied to mainline) in
> >
> > http://client.linux-nfs.org/Linux-2.6.x/2.6.23-rc1/linux-2.6.23-001-fix_rpciod_down_race.dif
>
> That fixed the problem -- still, do we care if we call async in
> gss_destroying_context? On umount the server drops out from under the
> tasks..

It is useful when running against Solaris RPC servers, since they will
actually respect the request to destroy the context. In the long run, we
should fix up Linux servers to do the same.

Cheers,
Trond