public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Benjamin Coddington <bcodding@redhat.com>,
	Trond Myklebust <trondmy@kernel.org>,
	Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, Lance Shelton <lance.shelton@hammerspace.com>
Subject: Re: [PATCH v3 0/3] NFS Client btime support
Date: Thu, 29 May 2025 07:06:09 -0400	[thread overview]
Message-ID: <f86d3e012b977959543f986cb99982d5047269f8.camel@kernel.org> (raw)
In-Reply-To: <cover.1748515333.git.bcodding@redhat.com>

On Thu, 2025-05-29 at 06:45 -0400, Benjamin Coddington wrote:
> 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.
> 
> v2 - fix unnecessary cast to printk
> v3 - drop hunk unrolling INVALID_ATTR on 2/3, add BTIME to INVALID_ATTR
> 
> 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            | 34 +++++++++++++++++++----
>  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    |  8 ++++++
>  include/linux/nfs_fs_sb.h |  2 +-
>  include/linux/nfs_xdr.h   | 57 ++++++++++++++++++++-------------------
>  8 files changed, 109 insertions(+), 36 deletions(-)

Reviewed-by: Jeff Layton <jlayton@kernel.org>

      parent reply	other threads:[~2025-05-29 11:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-29 10:45 [PATCH v3 0/3] NFS Client btime support Benjamin Coddington
2025-05-29 10:45 ` [PATCH v3 1/3] Expand the type of nfs_fattr->valid Benjamin Coddington
2025-05-29 10:45 ` [PATCH v3 2/3] nfs: Add timecreate to nfs inode Benjamin Coddington
2025-06-12  7:22   ` kernel test robot
2025-06-12 15:32     ` Benjamin Coddington
2025-06-17  8:48       ` Oliver Sang
2025-06-12 15:28   ` Benjamin Coddington
2025-05-29 10:45 ` [PATCH v3 3/3] NFS: Return the file btime in the statx results when appropriate Benjamin Coddington
2025-05-29 11:06 ` Jeff Layton [this message]

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=f86d3e012b977959543f986cb99982d5047269f8.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=anna@kernel.org \
    --cc=bcodding@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox