aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/linux/nfs_fs.h
diff options
context:
space:
mode:
authorTrond Myklebust <trond.myklebust@hammerspace.com>2022-08-26 19:44:44 -0400
committerTrond Myklebust <trond.myklebust@hammerspace.com>2022-11-27 22:09:59 -0500
commit0eb43812c0270ee3d005ff32f91f7d0a6c4943af (patch)
treee6dedf0052fee04071da4e7e65e7a733a90f9839 /include/linux/nfs_fs.h
parentLinux 6.1-rc7 (diff)
downloadwireguard-linux-0eb43812c0270ee3d005ff32f91f7d0a6c4943af.tar.xz
wireguard-linux-0eb43812c0270ee3d005ff32f91f7d0a6c4943af.zip
NFS: Clear the file access cache upon login
POSIX typically only refreshes the user's supplementary group information upon login. Since NFS servers may often refresh their concept of the user supplementary group membership at their own cadence, it is possible for the NFS client's access cache to become stale due to the user's group membership changing on the server after the user has already logged in on the client. While it is reasonable to expect that such group membership changes are rare, and that we do not want to optimise the cache to accommodate them, it is also not unreasonable for the user to expect that if they log out and log back in again, that the staleness would clear up. Reviewed-by: Benjamin Coddington <bcodding@redhat.com> Tested-by: Benjamin Coddington <bcodding@redhat.com> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'include/linux/nfs_fs.h')
-rw-r--r--include/linux/nfs_fs.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/include/linux/nfs_fs.h b/include/linux/nfs_fs.h
index 7931fa472561..d92fdfd2444c 100644
--- a/include/linux/nfs_fs.h
+++ b/include/linux/nfs_fs.h
@@ -59,6 +59,7 @@ struct nfs_access_entry {
kuid_t fsuid;
kgid_t fsgid;
struct group_info *group_info;
+ u64 timestamp;
__u32 mask;
struct rcu_head rcu_head;
};