public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFS: Do not set NFS_INO_INVALID_LABEL unless server supports labeled NFS
Date: Fri, 7 Feb 2014 15:21:05 +1100	[thread overview]
Message-ID: <20140207152105.2f0970e1@notabene.brown> (raw)
In-Reply-To: <1391716418-7353-1-git-send-email-trond.myklebust@primarydata.com>

[-- Attachment #1: Type: text/plain, Size: 4705 bytes --]

On Thu,  6 Feb 2014 14:53:38 -0500 Trond Myklebust
<trond.myklebust@primarydata.com> wrote:

> Commit aa9c2669626c (NFS: Client implementation of Labeled-NFS) introduces
> a performance regression. When nfs_zap_caches_locked is called, it sets
> the NFS_INO_INVALID_LABEL flag irrespectively of whether or not the
> NFS server supports security labels. Since that flag is never cleared,
> it means that all calls to nfs_revalidate_inode() will now trigger
> an on-the-wire GETATTR call.
> 
> This patch ensures that we never set the NFS_INO_INVALID_LABEL unless the
> server advertises support for labeled NFS.
> It also causes nfs_setsecurity() to clear NFS_INO_INVALID_LABEL when it
> has successfully set the security label for the inode.
> Finally it gets rid of the NFS_INO_INVALID_LABEL cruft from nfs_update_inode,
> which has nothing to do with labeled NFS.
> 
> Reported-by: Neil Brown <neilb@suse.de>
> Cc: stable@vger.kernel.org # 3.11+
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
> ---
> 
> Hi Neil,
> Does this fix the GETATTR regression that you reported?

Yes, thanks.
With this patch I don't get streams of GETATTR requests after the READDIR
request which I previously fixed with that oneline change in inode.c

Tested-by: NeilBrown <neilb@suse.de>

Thanks,
NeilBrown


> 
> Cheers
>  Trond
> 
>  fs/nfs/inode.c    | 14 ++++++++++----
>  fs/nfs/internal.h |  9 +++++++++
>  2 files changed, 19 insertions(+), 4 deletions(-)
> 
> diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c
> index 29cb93653b3c..4636b828e957 100644
> --- a/fs/nfs/inode.c
> +++ b/fs/nfs/inode.c
> @@ -169,7 +169,6 @@ static void nfs_zap_caches_locked(struct inode *inode)
>  	if (S_ISREG(mode) || S_ISDIR(mode) || S_ISLNK(mode)) {
>  		nfs_fscache_invalidate(inode);
>  		nfsi->cache_validity |= NFS_INO_INVALID_ATTR
> -					| NFS_INO_INVALID_LABEL
>  					| NFS_INO_INVALID_DATA
>  					| NFS_INO_INVALID_ACCESS
>  					| NFS_INO_INVALID_ACL
> @@ -177,10 +176,10 @@ static void nfs_zap_caches_locked(struct inode *inode)
>  		nfs_zap_readdir_cookie(nfsi);
>  	} else
>  		nfsi->cache_validity |= NFS_INO_INVALID_ATTR
> -					| NFS_INO_INVALID_LABEL
>  					| NFS_INO_INVALID_ACCESS
>  					| NFS_INO_INVALID_ACL
>  					| NFS_INO_REVAL_PAGECACHE;
> +	nfs_zap_label_cache_locked(nfsi);
>  }
>  
>  void nfs_zap_caches(struct inode *inode)
> @@ -272,6 +271,13 @@ nfs_init_locked(struct inode *inode, void *opaque)
>  }
>  
>  #ifdef CONFIG_NFS_V4_SECURITY_LABEL
> +static void nfs_clear_label_invalid(struct inode *inode)
> +{
> +	spin_lock(&inode->i_lock);
> +	NFS_I(inode)->cache_validity &= ~NFS_INO_INVALID_LABEL;
> +	spin_unlock(&inode->i_lock);
> +}
> +
>  void nfs_setsecurity(struct inode *inode, struct nfs_fattr *fattr,
>  					struct nfs4_label *label)
>  {
> @@ -289,6 +295,7 @@ void nfs_setsecurity(struct inode *inode, struct nfs_fattr *fattr,
>  					__func__,
>  					(char *)label->label,
>  					label->len, error);
> +		nfs_clear_label_invalid(inode);
>  	}
>  }
>  
> @@ -1654,7 +1661,7 @@ static int nfs_update_inode(struct inode *inode, struct nfs_fattr *fattr)
>  		inode->i_blocks = fattr->du.nfs2.blocks;
>  
>  	/* Update attrtimeo value if we're out of the unstable period */
> -	if (invalid & (NFS_INO_INVALID_ATTR|NFS_INO_INVALID_LABEL)) {
> +	if (invalid & NFS_INO_INVALID_ATTR) {
>  		nfs_inc_stats(inode, NFSIOS_ATTRINVALIDATE);
>  		nfsi->attrtimeo = NFS_MINATTRTIMEO(inode);
>  		nfsi->attrtimeo_timestamp = now;
> @@ -1667,7 +1674,6 @@ static int nfs_update_inode(struct inode *inode, struct nfs_fattr *fattr)
>  		}
>  	}
>  	invalid &= ~NFS_INO_INVALID_ATTR;
> -	invalid &= ~NFS_INO_INVALID_LABEL;
>  	/* Don't invalidate the data if we were to blame */
>  	if (!(S_ISREG(inode->i_mode) || S_ISDIR(inode->i_mode)
>  				|| S_ISLNK(inode->i_mode)))
> diff --git a/fs/nfs/internal.h b/fs/nfs/internal.h
> index 8b5cc04a8611..fafdddac8271 100644
> --- a/fs/nfs/internal.h
> +++ b/fs/nfs/internal.h
> @@ -279,9 +279,18 @@ static inline void nfs4_label_free(struct nfs4_label *label)
>  	}
>  	return;
>  }
> +
> +static inline void nfs_zap_label_cache_locked(struct nfs_inode *nfsi)
> +{
> +	if (nfs_server_capable(&nfsi->vfs_inode, NFS_CAP_SECURITY_LABEL))
> +		nfsi->cache_validity |= NFS_INO_INVALID_LABEL;
> +}
>  #else
>  static inline struct nfs4_label *nfs4_label_alloc(struct nfs_server *server, gfp_t flags) { return NULL; }
>  static inline void nfs4_label_free(void *label) {}
> +static inline void nfs_zap_label_cache_locked(struct nfs_inode *nfsi)
> +{
> +}
>  #endif /* CONFIG_NFS_V4_SECURITY_LABEL */
>  
>  /* proc.c */


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-02-07  4:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-04 14:47 readdir vs. getattr Tigran Mkrtchyan
2013-04-04 15:15 ` Jim Rees
2013-04-04 15:32   ` Chuck Lever
2013-04-04 16:01     ` Jim Rees
2013-04-04 16:15       ` Myklebust, Trond
2013-04-04 16:35         ` Jim Rees
2013-04-04 18:28           ` Tigran Mkrtchyan
2013-04-04 15:38   ` Tigran Mkrtchyan
2013-04-04 15:48     ` Myklebust, Trond
2013-04-04 15:52       ` Tigran Mkrtchyan
2014-01-29  7:10       ` NeilBrown
2014-01-29  7:25       ` NeilBrown
2014-01-29  9:21         ` Mkrtchyan, Tigran
2014-01-29 12:18           ` Jeff Layton
2014-02-06  2:45             ` NeilBrown
2014-02-06  2:51               ` NeilBrown
2014-02-06 18:08                 ` Jeff Layton
2014-02-06 19:53                 ` [PATCH] NFS: Do not set NFS_INO_INVALID_LABEL unless server supports labeled NFS Trond Myklebust
2014-02-07  4:21                   ` NeilBrown [this message]
2014-02-06 22:12                 ` readdir vs. getattr Trond Myklebust
2014-02-07  4:30                   ` NeilBrown
2014-02-07 19:47                     ` Trond Myklebust
2014-02-07 22:08                       ` Trond Myklebust
2014-02-10  0:16                         ` NeilBrown

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=20140207152105.2f0970e1@notabene.brown \
    --to=neilb@suse.de \
    --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