Linux NFS development
 help / color / mirror / Atom feed
From: Steve Dickson <steved@redhat.com>
To: Chengen Du <chengen.du@canonical.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v3] nfs(5): adding new mount option 'fasc'
Date: Fri, 10 Nov 2023 11:54:30 -0500	[thread overview]
Message-ID: <6b4e6cd5-5711-4033-b813-2f8048c35921@redhat.com> (raw)
In-Reply-To: <20230828055324.21408-1-chengen.du@canonical.com>

Hello,

My apologies on this delay...

On 8/28/23 1:53 AM, Chengen Du wrote:
> Add an option that triggers the clearing of the file
> access cache as soon as the cache timestamp becomes
> older than the user's login time.
> 
> Signed-off-by: Chengen Du <chengen.du@canonical.com>
On a 6.7-rc0 kernel I'm getting "nfs: Unknown parameter 'fasc'"
error... was this never implemented?

steved.

> ---
>   utils/mount/nfs.man | 13 +++++++++++++
>   1 file changed, 13 insertions(+)
> 
> diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
> index 9b4bc9c9..2ac7b4ad 100644
> --- a/utils/mount/nfs.man
> +++ b/utils/mount/nfs.man
> @@ -608,6 +608,19 @@ option is not specified,
>   the default behavior depends on the kernel version,
>   but is usually equivalent to
>   .BR "xprtsec=none" .
> +.TP 1.5i
> +.BI fasc
> +Triggers the clearing of the file access cache as soon as the cache
> +timestamp becomes older than the user's login time. It is supported
> +in kernels 6.4 and later.
> +.IP
> +NFS servers often refresh their users' group membership at their
> +own cadence, which means the NFS client's file access cache can
> +become stale if the user's group membership changes on the server
> +after they've logged in on the client. To align with the principles
> +of the POSIX design, which only refreshes the user's supplementary
> +group information upon login, the mechanism uses the user's login
> +time to determine whether the file access cache needs to be refreshed.
>   .SS "Options for NFS versions 2 and 3 only"
>   Use these options, along with the options in the above subsection,
>   for NFS versions 2 and 3 only.


  reply	other threads:[~2023-11-10 18:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-28  5:53 [PATCH v3] nfs(5): adding new mount option 'fasc' Chengen Du
2023-11-10 16:54 ` Steve Dickson [this message]
2023-11-10 19:08   ` Trond Myklebust
2023-11-11 14:44     ` Steve Dickson
2023-11-14  9:31       ` Daire Byrne

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=6b4e6cd5-5711-4033-b813-2f8048c35921@redhat.com \
    --to=steved@redhat.com \
    --cc=chengen.du@canonical.com \
    --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