diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2026-05-07 04:53:07 -0400 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-05-11 16:50:30 +0200 |
| commit | 01ee7c3d2e23b41cc3f285e69b474f4e0890cce9 (patch) | |
| tree | fc8af068b1c6dfb755c0eaf705a9b1be817fdbe4 /drivers/platform/wmi/tests/git@git.tavy.me:linux.git | |
| parent | 211cb2ba487706a55c1bb4e572a89d7e7835930a (diff) | |
nfsd: Implement NFSv4 FATTR4_CASE_INSENSITIVE and FATTR4_CASE_PRESERVING
NFSD currently provides NFSv4 clients with hard-coded responses
indicating all exported filesystems are case-sensitive and
case-preserving. This is incorrect for case-insensitive filesystems
and ext4 directories with casefold enabled.
Query the underlying filesystem's actual case sensitivity via
nfsd_get_case_info() and return accurate values to clients. This
supports per-directory settings for filesystems that allow mixing
case-sensitive and case-insensitive directories within an export.
The helper queries the parent dentry for non-directory filehandles
because case-folding is a per-directory property. That resolution
has the same corner cases here as for NFSv3 PATHCONF: single-file
exports query an unexported parent, disconnected dentries report
defaults until reconnected, and hardlinked files track whichever
alias the dcache currently holds.
Reviewed-by: Roland Mainz <roland.mainz@nrubsig.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Link: https://patch.msgid.link/20260507-case-sensitivity-v14-14-e62cc8200435@oracle.com
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'drivers/platform/wmi/tests/git@git.tavy.me:linux.git')
0 files changed, 0 insertions, 0 deletions
