linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@primarydata.com>
Cc: linux-nfs@vger.kernel.org, trond.myklebust@primarydata.com,
	hch@infradead.org
Subject: Re: [PATCH v2 0/4] nfsd: don't let nfs4_file pin down the inode when it has no open state
Date: Wed, 23 Jul 2014 16:47:12 -0400	[thread overview]
Message-ID: <20140723204712.GI9118@fieldses.org> (raw)
In-Reply-To: <1406146661-9794-1-git-send-email-jlayton@primarydata.com>

On Wed, Jul 23, 2014 at 04:17:37PM -0400, Jeff Layton wrote:
> This is a port of the patches that Trond sent the other day onto the
> current tip of Bruce's for-3.17 branch. It basically changes how
> nfs4_file objects are hashed. Instead of using the inode pointer (and
> pinning down an inode in the process), it uses the filehandle. This
> allows us to avoid taking an inode reference directly for the nfs4_file.
> With this, they're only taken by virtue of the files in the fi_fds
> array.

Looks OK to me.  I'll give it a day in case Christoph or someone spots a
problem.

--b.

> 
> Jeff Layton (1):
>   nfsd: Do not let nfs4_file pin the struct inode
> 
> Trond Myklebust (3):
>   nfsd: Store the filehandle with the struct nfs4_file
>   nfsd: Use the filehandle to look up the struct nfs4_file instead of
>     inode
>   nfsd: nfs4_check_fh - make it actually check the filehandle
> 
>  fs/nfsd/nfs4state.c | 86 +++++++++++++++++++++++++++++++++--------------------
>  fs/nfsd/state.h     |  2 +-
>  2 files changed, 54 insertions(+), 34 deletions(-)
> 
> -- 
> 1.9.3
> 

  parent reply	other threads:[~2014-07-23 20:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-23 20:17 [PATCH v2 0/4] nfsd: don't let nfs4_file pin down the inode when it has no open state Jeff Layton
2014-07-23 20:17 ` [PATCH v2 1/4] nfsd: Store the filehandle with the struct nfs4_file Jeff Layton
2014-07-23 20:17 ` [PATCH v2 2/4] nfsd: Use the filehandle to look up the struct nfs4_file instead of inode Jeff Layton
2014-07-23 20:17 ` [PATCH v2 3/4] nfsd: nfs4_check_fh - make it actually check the filehandle Jeff Layton
2014-07-23 20:17 ` [PATCH v2 4/4] nfsd: Do not let nfs4_file pin the struct inode Jeff Layton
2014-07-23 20:47 ` J. Bruce Fields [this message]
2014-07-24 15:22   ` [PATCH v2 0/4] nfsd: don't let nfs4_file pin down the inode when it has no open state Christoph Hellwig
2014-07-25  1:40     ` J. Bruce Fields

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=20140723204712.GI9118@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=hch@infradead.org \
    --cc=jlayton@primarydata.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.com \
    /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).