Linux NFS development
 help / color / mirror / Atom feed
From: bfields@fieldses.org (J. Bruce Fields)
To: trondmy@kernel.org
Cc: Anna Schumaker <anna.schumaker@netapp.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/5] Support case insensitive filesystems in NFSv4
Date: Mon, 3 Jan 2022 15:08:47 -0500	[thread overview]
Message-ID: <20220103200847.GH21514@fieldses.org> (raw)
In-Reply-To: <20211217203658.439352-1-trondmy@kernel.org>

On Fri, Dec 17, 2021 at 03:36:53PM -0500, trondmy@kernel.org wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
> 
> Add support for detecting an export of a case insensitive filesystem in
> NFSv4. If that is the case, then we need to adjust the dentry caching
> and invalidation rules to ensure that we don't inadvertently end up
> caching other case folded aliases after an operation that results in a
> directory entry name change.

What server and configuration are you testing this against?

--b.

> 
> Trond Myklebust (5):
>   NFSv4: Add some support for case insensitive filesystems
>   NFSv4: Just don't cache negative dentries on case insensitive servers
>   NFS: Invalidate negative dentries on all case insensitive directory
>     changes
>   NFS: Add a helper to remove case-insensitive aliases
>   NFS: Fix the verifier for case sensitive filesystem in
>     nfs_atomic_open()
> 
>  fs/nfs/dir.c              | 41 +++++++++++++++++++++++++++++++++------
>  fs/nfs/internal.h         |  1 +
>  fs/nfs/nfs4proc.c         | 13 +++++++++++--
>  fs/nfs/nfs4xdr.c          | 40 ++++++++++++++++++++++++++++++++++++++
>  include/linux/nfs_fs_sb.h |  2 ++
>  include/linux/nfs_xdr.h   |  2 ++
>  6 files changed, 91 insertions(+), 8 deletions(-)
> 
> -- 
> 2.33.1

  parent reply	other threads:[~2022-01-03 20:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 20:36 [PATCH 0/5] Support case insensitive filesystems in NFSv4 trondmy
2021-12-17 20:36 ` [PATCH 1/5] NFSv4: Add some support for case insensitive filesystems trondmy
2021-12-17 20:36   ` [PATCH 2/5] NFSv4: Just don't cache negative dentries on case insensitive servers trondmy
2021-12-17 20:36     ` [PATCH 3/5] NFS: Invalidate negative dentries on all case insensitive directory changes trondmy
2021-12-17 20:36       ` [PATCH 4/5] NFS: Add a helper to remove case-insensitive aliases trondmy
2021-12-17 20:36         ` [PATCH 5/5] NFS: Fix the verifier for case sensitive filesystem in nfs_atomic_open() trondmy
2022-01-03 20:08 ` J. Bruce Fields [this message]
2022-01-03 20:11   ` [PATCH 0/5] Support case insensitive filesystems in NFSv4 Trond Myklebust
2022-01-03 21:46     ` bfields
2022-01-03 22:13       ` Trond Myklebust

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=20220103200847.GH21514@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trondmy@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