linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: Chengen Du <chengen.du@canonical.com>
Cc: Anna Schumaker <anna@kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NFS: Correct timing for assigning access cache timestamp
Date: Tue, 14 Mar 2023 18:51:24 +0000	[thread overview]
Message-ID: <84E89457-478E-42F8-AC5F-DFFC58FBEFFB@hammerspace.com> (raw)
In-Reply-To: <20230308080327.33906-1-chengen.du@canonical.com>



> On Mar 8, 2023, at 03:03, Chengen Du <chengen.du@canonical.com> wrote:
> 
> When the user's login time is newer than the cache's timestamp,
> the original entry in the RB-tree will be replaced by a new entry.
> Currently, the timestamp is only set if the entry is not found in
> the RB-tree, which can cause the timestamp to be undefined when
> the entry exists. This may result in a significant increase in
> ACCESS operations if the timestamp is set to zero.
> 
> Signed-off-by: Chengen Du <chengen.du@canonical.com>
> ---
> fs/nfs/dir.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/fs/nfs/dir.c b/fs/nfs/dir.c
> index a41c3ee4549c..6fbcbb8d6587 100644
> --- a/fs/nfs/dir.c
> +++ b/fs/nfs/dir.c
> @@ -3089,7 +3089,6 @@ static void nfs_access_add_rbtree(struct inode *inode,
> else
> goto found;
> }
> - set->timestamp = ktime_get_ns();
> rb_link_node(&set->rb_node, parent, p);
> rb_insert_color(&set->rb_node, root_node);
> list_add_tail(&set->lru, &nfsi->access_cache_entry_lru);
> @@ -3114,6 +3113,7 @@ void nfs_access_add_cache(struct inode *inode, struct nfs_access_entry *set,
> cache->fsgid = cred->fsgid;
> cache->group_info = get_group_info(cred->group_info);
> cache->mask = set->mask;
> + cache->timestamp = ktime_get_ns();
> 
> /* The above field assignments must be visible
> * before this item appears on the lru.  We cannot easily
> -- 
> 2.37.2
> 

Doh! Nice catch…

Anna, please pick this up for 6.2-rcX and add an appropriate

Fixes: 0eb43812c027 ("NFS: Clear the file access cache upon login”)

Thanks!
  Trond

_________________________________
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com


  parent reply	other threads:[~2023-03-14 18:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  8:03 [PATCH] NFS: Correct timing for assigning access cache timestamp Chengen Du
2023-03-08 14:45 ` Benjamin Coddington
2023-03-10  2:57   ` Chengen Du
2023-03-14 18:51 ` Trond Myklebust [this message]
2023-03-14 19:47   ` Anna Schumaker

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=84E89457-478E-42F8-AC5F-DFFC58FBEFFB@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=anna@kernel.org \
    --cc=chengen.du@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --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).