From: Benjamin Coddington <bcodding@redhat.com>
To: Trond Myklebust <trondmy@kernel.org>, Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, Lance Shelton <lance.shelton@hammerspace.com>
Subject: [PATCH v1 0/3] NFS Client btime support
Date: Thu, 15 May 2025 10:40:15 -0400 [thread overview]
Message-ID: <cover.1747318805.git.bcodding@redhat.com> (raw)
We're getting requests to allow the client to support btime, current kNFSD
already supports this for compatible filesystems.
I've rebased and worked the first three patches from
https://lore.kernel.org/linux-nfs/20211227190504.309612-1-trondmy@kernel.org/
onto v6.14, and I've been driving them around bakeathon without any signs
of trouble yet this week.
Thanks Trond and Anne for this (years-ago) work.
Anne Marie Merritt (1):
nfs: Add timecreate to nfs inode
Trond Myklebust (2):
Expand the type of nfs_fattr->valid
NFS: Return the file btime in the statx results when appropriate
fs/nfs/inode.c | 48 ++++++++++++++++++++++++++-------
fs/nfs/nfs4proc.c | 14 +++++++++-
fs/nfs/nfs4trace.h | 3 ++-
fs/nfs/nfs4xdr.c | 24 +++++++++++++++++
fs/nfs/nfstrace.h | 3 ++-
include/linux/nfs_fs.h | 7 +++++
include/linux/nfs_fs_sb.h | 2 +-
include/linux/nfs_xdr.h | 57 ++++++++++++++++++++-------------------
8 files changed, 117 insertions(+), 41 deletions(-)
--
2.47.0
next reply other threads:[~2025-05-15 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 14:40 Benjamin Coddington [this message]
2025-05-15 14:40 ` [PATCH v1 1/3] Expand the type of nfs_fattr->valid Benjamin Coddington
2025-05-16 15:05 ` Jeff Layton
2025-05-16 15:31 ` Benjamin Coddington
2025-05-27 21:26 ` Anna Schumaker
2025-05-28 0:09 ` Benjamin Coddington
2025-05-15 14:40 ` [PATCH v1 2/3] nfs: Add timecreate to nfs inode Benjamin Coddington
2025-05-15 14:40 ` [PATCH v1 3/3] NFS: Return the file btime in the statx results when appropriate Benjamin Coddington
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.1747318805.git.bcodding@redhat.com \
--to=bcodding@redhat.com \
--cc=anna@kernel.org \
--cc=lance.shelton@hammerspace.com \
--cc=linux-nfs@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.