All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever III <chuck.lever@oracle.com>
To: Dan Shelton <dan.f.shelton@gmail.com>
Cc: Chen Hanxiao <chenhx.fnst@fujitsu.com>,
	Trond Myklebust <trond.myklebust@hammerspace.com>,
	Anna Schumaker <anna@kernel.org>,
	Jeff Layton <jlayton@kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfsv4: Add support for the birth time attribute
Date: Tue, 16 Jan 2024 01:43:18 +0000	[thread overview]
Message-ID: <0CDB9C6D-5BC7-4E99-8B08-825424D0DD4F@oracle.com> (raw)
In-Reply-To: <CAAvCNcDxZF-ftqb1dRnjUW-q-1m2kyqN-MAGNXUd+i1r_b_vSQ@mail.gmail.com>



> On Jan 15, 2024, at 8:02 PM, Dan Shelton <dan.f.shelton@gmail.com> wrote:
> 
> On Mon, 15 Jan 2024 at 07:37, Chen Hanxiao <chenhx.fnst@fujitsu.com> wrote:
>> 
>> This patch enable nfs to report btime in nfs_getattr.
>> If underlying filesystem supports "btime" timestamp,
>> statx will report btime for STATX_BTIME.
>> 
>> Signed-off-by: Chen Hanxiao <chenhx.fnst@fujitsu.com>
>> ---
>> v1:
>>    Don't revalidate btime attribute
>> 
>> RFC v2:
>>    properly set cache validity
>> 
>> fs/nfs/inode.c          | 23 ++++++++++++++++++++---
>> fs/nfs/nfs4proc.c       |  3 +++
>> fs/nfs/nfs4xdr.c        | 23 +++++++++++++++++++++++
>> include/linux/nfs_fs.h  |  2 ++
>> include/linux/nfs_xdr.h |  5 ++++-
>> 5 files changed, 52 insertions(+), 4 deletions(-)#
> 
> Hello
> 
> Where is the patch which adds support for btime to nfsd?

Support for the birth time attribute was added to NFSD two years
ago by commit e377a3e698fb ("nfsd: Add support for the birth
time attribute").


--
Chuck Lever



  reply	other threads:[~2024-01-16  1:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-15  6:36 [PATCH] nfsv4: Add support for the birth time attribute Chen Hanxiao
2024-01-15 19:41 ` Cedric Blancher
2024-01-16  1:02 ` Dan Shelton
2024-01-16  1:43   ` Chuck Lever III [this message]
2024-01-16 20:17     ` Dan Shelton
2024-01-17  2:54       ` Chuck Lever III
2024-01-17  3:53         ` 回复: " Hanxiao Chen (Fujitsu)
2024-01-17  3:13       ` Hanxiao Chen (Fujitsu)

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=0CDB9C6D-5BC7-4E99-8B08-825424D0DD4F@oracle.com \
    --to=chuck.lever@oracle.com \
    --cc=anna@kernel.org \
    --cc=chenhx.fnst@fujitsu.com \
    --cc=dan.f.shelton@gmail.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@hammerspace.com \
    /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.