Received-SPF: pass (google.com: domain of linux-nfs+bounces-2025-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Precedence: bulk
MIME-Version: 1.0
From: Dan Shelton <dan.f.shelton@gmail.com>
Date: Mon, 19 Feb 2024 03:14:52 +0100
Message-ID: <CAAvCNcACKjaSnnWj71y8GkHN25G=vmDAgif83eaP+d_XF6pBpg@mail.gmail.com>
Subject: Understanding NFSv4 client attribute caching
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"

Hello!

I just try to understand NFSv4 client-side attribute caching, if I do
a nfs4client_setattr(), which attribute values can be updated in the
clients cache, and which should be invalidated, and then reloaded from
the server?

For example if I do a nfs4client_setattr(FATTR4_WORD1_OWNER, "myusr1@mydom"):

Can I cache  "myusr1@mydom" as the new user on the client side on
success, or should I invalidate the cache, because maybe the idmapd on
the server changed the user name, or exports all_squash option
squashed the user name to nobody?

Dan
-- 
Dan Shelton - Cluster Specialist Win/Lin/Bsd