diff options
| author | Chuck Lever <chuck.lever@oracle.com> | 2026-05-15 11:35:11 -0400 |
|---|---|---|
| committer | Christian Brauner <brauner@kernel.org> | 2026-05-15 17:49:22 +0200 |
| commit | 425294293cd11a05e46278c21cc674780e02fef1 (patch) | |
| tree | 73fb9682decdfdfb974c862d6aff244519c3aa74 /drivers/platform/wmi/tests/git@git.tavy.me:linux.git | |
| parent | c6eb07d3da833c351993ab8582c27073afe295e6 (diff) | |
nfs: Skip pathconf probe when neither field is consumed
The PATHCONF RPC issued from nfs_probe_fsinfo() supplies two pieces of
information: max_namelen, used only when server->namelen has not been
pinned by mount options, and the case_insensitive / case_preserving
fields, used only by the NFSv2/NFSv3 path. NFSv4 receives its case
sensitivity caps from the FATTR4_CASE_* attributes during the
set_capabilities probe, and a non-zero server->namelen short-circuits
the only other field of interest.
When both conditions hold (NFSv4 with namelen pinned), the pathconf
reply is discarded in full but the round-trip is still on the mount
critical path. Gate the call on version < 4 || namelen == 0 so that
mounts which cannot benefit from the reply do not pay for it.
Reported-by: sashiko-bot <sashiko-bot@kernel.org>
Closes: https://sashiko.dev/#/patchset/20260507-case-sensitivity-v14-0-e62cc8200435@oracle.com?part=10
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Link: https://patch.msgid.link/20260515153515.362266-4-cel@kernel.org
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
