linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: linux-nfs@vger.kernel.org
Subject: Umount and delegation release thread syncronization
Date: Mon, 20 Jun 2011 15:45:29 +0800	[thread overview]
Message-ID: <1308555929.3306.43.camel@perseus.themaw.net> (raw)

Hi all,

I'm having difficulty working out how delegation release threads are
synchronized with umount.

For an information about the problem please see
https://bugzilla.kernel.org/show_bug.cgi?id=30882 and in particular
comment #28.

Can someone please give me a description of the sequence of events at
umount (aka. nfs4_kill_super() function calls). In particular how does
nfs_free_server() know that if nfs_super_return_all_delegations() starts
a thread that it is finished before freeing the server struct.

Any information or observations about the opps in the above bug would
also be appreciated.

Ian



             reply	other threads:[~2011-06-20  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20  7:45 Ian Kent [this message]
2011-07-12  3:51 ` Umount and delegation release thread syncronization Ian Kent
2011-07-25 19:30   ` 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=1308555929.3306.43.camel@perseus.themaw.net \
    --to=raven@themaw.net \
    --cc=linux-nfs@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).