linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@kernel.org>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/2] Fixes for the NFS automounter
Date: Sun,  3 Aug 2025 18:29:27 -0700	[thread overview]
Message-ID: <cover.1754270543.git.trond.myklebust@hammerspace.com> (raw)

From: Trond Myklebust <trond.myklebust@hammerspace.com>

This series addresses 2 sets of issues with the NFS automount
functionality:

1. Capabilities are being inherited from the parent directory instead
   of assuming that the subdirectory may have different properties than
   the parent. This is particularly problematic when the parent is a
   referral.
2. We appear to be repeating some operations unnecessarily when
   traversing a submount point.

Trond Myklebust (2):
  NFS: Fix the setting of capabilities when automounting a new
    filesystem
  NFSv4: Remove duplicate lookups, capability probes and fsinfo calls

 fs/nfs/client.c      | 44 +++++++++++++++++++++-
 fs/nfs/internal.h    |  2 +-
 fs/nfs/nfs4_fs.h     |  5 ++-
 fs/nfs/nfs4client.c  | 20 +---------
 fs/nfs/nfs4getroot.c | 14 +++----
 fs/nfs/nfs4proc.c    | 89 ++++++++++++++++++++------------------------
 6 files changed, 93 insertions(+), 81 deletions(-)

-- 
2.50.1


             reply	other threads:[~2025-08-04  1:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-04  1:29 Trond Myklebust [this message]
2025-08-04  1:29 ` [PATCH 1/2] NFS: Fix the setting of capabilities when automounting a new filesystem Trond Myklebust
2025-08-04 16:07   ` Benjamin Coddington
2025-08-04  1:29 ` [PATCH 2/2] NFSv4: Remove duplicate lookups, capability probes and fsinfo calls Trond Myklebust
2025-08-04 16:43   ` Benjamin Coddington
2025-08-04 16:54     ` Trond Myklebust
2025-08-04 19:07       ` Benjamin Coddington
2025-08-05 13:35         ` Benjamin Coddington
2025-08-24  7:00 ` [PATCH 0/2] Fixes for the NFS automounter Scott Haiden

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=cover.1754270543.git.trond.myklebust@hammerspace.com \
    --to=trondmy@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).