linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "bfields@fieldses.org" <bfields@fieldses.org>
To: Ondrej Valousek <ondrej.valousek.xm@renesas.com>
Cc: Trond Myklebust <trondmy@hammerspace.com>,
	"trondmy@kernel.org" <trondmy@kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>
Subject: Re: [PATCH 0/8] Support btime and other NFSv4 specific attributes
Date: Wed, 5 Jan 2022 10:10:08 -0500	[thread overview]
Message-ID: <20220105151008.GB24685@fieldses.org> (raw)
In-Reply-To: <DU2PR10MB5096010E9570E2718198EDD5E14B9@DU2PR10MB5096.EURPRD10.PROD.OUTLOOK.COM>

On Wed, Jan 05, 2022 at 03:05:17PM +0000, Ondrej Valousek wrote:
> Sorry for confusion and maybe dumb questions:
> - The aim is to transfer these attributes via RFC8276 (File System Extended attributes in NFSv4)?

No, NFSv4 defines attributes for all of these.

RFC8276 attributes are purely for user-defined attribues, not for
anything that the server or filesystem gives specific meaning.

> - AFAIK support for RFC8276 in NFS (only version 4.2) server is since kernel 5.9, right? NFS client supports these as well?
> - The patches below implements the feature in both, nfs client AND server, right?

Client only.

These would probably be quite easy to support on the server side when
the filesystem supports them, but nobody's volunteered to implement
that yet; patches welcome.

--b.

  parent reply	other threads:[~2022-01-05 15:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 20:48 [PATCH 0/8] Support btime and other NFSv4 specific attributes trondmy
2021-12-17 20:48 ` [PATCH 1/8] NFS: Expand the type of nfs_fattr->valid trondmy
2021-12-17 20:48   ` [PATCH 2/8] nfs: Add timecreate to nfs inode trondmy
2021-12-17 20:48     ` [PATCH 3/8] NFS: Return the file btime in the statx results when appropriate trondmy
2021-12-17 20:48       ` [PATCH 4/8] nfs: Add 'archive', 'hidden' and 'system' fields to nfs inode trondmy
2021-12-17 20:48         ` [PATCH 5/8] nfs: Add 'time backup' " trondmy
2021-12-17 20:48           ` [PATCH 6/8] NFSv4: Support the offline bit trondmy
2021-12-17 20:48             ` [PATCH 7/8] NFS: Support statx_get and statx_set ioctls trondmy
2021-12-17 20:48               ` [PATCH 8/8] NFSv4: Add an ioctl to allow retrieval of the NFS raw ACCESS mask trondmy
2021-12-21 22:20                 ` Anna Schumaker
2022-01-03 20:52               ` [PATCH 7/8] NFS: Support statx_get and statx_set ioctls J. Bruce Fields
2022-01-03 20:56                 ` Trond Myklebust
2022-01-03 21:47                   ` bfields
2022-01-03 20:51 ` [PATCH 0/8] Support btime and other NFSv4 specific attributes J. Bruce Fields
2022-01-03 20:51   ` Trond Myklebust
2022-01-05 15:05     ` Ondrej Valousek
2022-01-05 15:10       ` Trond Myklebust
2022-01-05 15:10       ` bfields [this message]
2022-01-05 15:40         ` Ondrej Valousek
2022-01-05 15:54           ` bfields
2022-01-06  9:31             ` Ondrej Valousek
2022-01-06 14:15               ` Trond Myklebust
2022-01-06 14:19                 ` Ondrej Valousek
2022-01-06 14:28                   ` bfields
2022-01-06 14:36                     ` bfields
2022-01-06 14:52                       ` Ondrej Valousek
2022-01-06 14:55                         ` bfields
2022-01-06 16:13                           ` Ondrej Valousek
2022-01-06 16:59                             ` Chuck Lever III
2022-01-06 18:47   ` Olga Kornievskaia

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=20220105151008.GB24685@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=anna.schumaker@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=ondrej.valousek.xm@renesas.com \
    --cc=trondmy@hammerspace.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;
as well as URLs for NNTP newsgroup(s).