mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>,
	 Lance Shelton <lance.shelton@hammerspace.com>,
	 Olga Kornievskaia <okorniev@redhat.com>
Cc: Thomas Haynes <loghyr@gmail.com>,
	linux-nfs@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Jeff Layton <jlayton@kernel.org>
Subject: [PATCH v2 0/3] NFS: fixes for delegated timestamps
Date: Mon, 09 Nov 2026 15:44:46 -0500	[thread overview]
Message-ID: <20261109-delegts-nfs-v2-0-9d1e926cc3d5@kernel.org> (raw)

This version fixes some issues that Sashiko pointed out.

These are some client-side fixes for problems that I was seeing with
delegated timestamps. Mostly this was evident in the git regression
testsuite (which is particularly sensitive to timestamp issues).

Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
Changes in v2:
- "don't let delegated c/mtime stamps go backward": compute the stamp
  before storing it, so lockless readers never see the coarse time
- "stamp after the server's ctime when truncating under delegated times":
  stamp before nfs_vmtruncate() drops i_lock
- "stamp after the server's ctime following a CLONE":
  - stamp under i_lock
  - apply the reply with nfs_refresh_inode() under delegated times, so
    its ctime doesn't overwrite the stamp
- Link to v1: https://lore.kernel.org/r/20261106-delegts-nfs-v1-0-1d5c5e364a07@kernel.org

---
Jeff Layton (3):
      NFS: don't let delegated c/mtime stamps go backward
      NFS: stamp after the server's ctime when truncating under delegated times
      NFS: stamp after the server's ctime following a CLONE

 fs/nfs/delegation.h |  2 ++
 fs/nfs/inode.c      | 65 ++++++++++++++++++++++++++++++++++++++++-------------
 fs/nfs/nfs42proc.c  | 25 ++++++++++++++++-----
 3 files changed, 72 insertions(+), 20 deletions(-)
---
base-commit: 5e810a57a1cf2fc785d89e711ff40f1112f6404c
change-id: 20261106-delegts-nfs-25dafe47b434

Best regards,
-- 
Jeff Layton <jlayton@kernel.org>


             reply	other threads:[~2026-11-09 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 20:44 Jeff Layton [this message]
2026-11-09 20:44 ` [PATCH v2 1/3] NFS: don't let delegated c/mtime stamps go backward Jeff Layton
2026-11-09 20:44 ` [PATCH v2 2/3] NFS: stamp after the server's ctime when truncating under delegated times Jeff Layton
2026-11-09 20:44 ` [PATCH v2 3/3] NFS: stamp after the server's ctime following a CLONE Jeff Layton

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=20261109-delegts-nfs-v2-0-9d1e926cc3d5@kernel.org \
    --to=jlayton@kernel.org \
    --cc=anna@kernel.org \
    --cc=lance.shelton@hammerspace.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=loghyr@gmail.com \
    --cc=okorniev@redhat.com \
    --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

all inboxes | Powered by JetHome®