From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Neil Brown <neilb@suse.de>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Strange lockup during unmount in 2.6.22 - maybe rpciod deadlock?
Date: Thu, 10 Jan 2008 20:26:32 -0500 [thread overview]
Message-ID: <1200014792.20100.11.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <18310.49514.808155.132856-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
On Fri, 2008-01-11 at 12:07 +1100, Neil Brown wrote:
> The only fix that occurs to me is to use schedule_work to shunt the
> rpc_shutdown_client into a separate thread.
Well. Instead of rpc_shutdown_client() you could use
rpc_release_client() in order to have the last RPC caller destroy the
client when the last rpc_task exits.
The problem then is that you lose the guarantee that all RPC tasks must
complete before you free structures such as the nfs_server...
Cheers
Trond
next prev parent reply other threads:[~2008-01-11 1:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 21:51 Strange lockup during unmount in 2.6.22 - maybe rpciod deadlock? Neil Brown
[not found] ` <18310.37731.29874.582772-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-01-10 22:41 ` Trond Myklebust
2008-01-11 1:07 ` Neil Brown
[not found] ` <18310.49514.808155.132856-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-01-11 1:26 ` Trond Myklebust [this message]
[not found] ` <1200004896.13775.27.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-14 19:01 ` Benjamin Coddington
2008-01-14 19:31 ` Trond Myklebust
[not found] ` <1200339108.7470.45.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-14 20:28 ` Benjamin Coddington
2008-01-14 20:36 ` Trond Myklebust
[not found] ` <1200343018.7470.56.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-14 21:09 ` J. Bruce Fields
2008-02-19 5:34 ` Neil Brown
[not found] ` <18362.27251.619125.502340-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-02-19 19:26 ` Trond Myklebust
[not found] ` <1203449166.8156.85.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-02-19 23:18 ` Trond Myklebust
2008-02-21 5:16 ` Neil Brown
[not found] ` <18365.2329.495660.107605-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-02-21 13:34 ` Trond Myklebust
2008-02-21 4:58 ` Neil Brown
[not found] ` <18365.1274.387629.944796-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-02-21 12:16 ` Jeff Layton
2008-02-21 15:27 ` Trond Myklebust
2008-02-22 0:31 ` Neil Brown
[not found] ` <18366.6141.122127.181304-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2008-02-22 0:41 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1200014792.20100.11.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.