Linux NFS development
 help / color / mirror / Atom feed
From: Benjamin Coddington <bcodding@redhat.com>
To: Trond Myklebust <trondmy@kernel.org>
Cc: anna@kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/8] Support btime and other NFSv4 specific attributes
Date: Tue, 27 May 2025 20:08:27 -0400	[thread overview]
Message-ID: <1C356965-867D-48B2-BAB1-C63FD6533CE0@redhat.com> (raw)
In-Reply-To: <cb113c0832d61ddddde7f01b3b78eb877a1f8cc5.camel@kernel.org>

On 27 May 2025, at 17:54, Trond Myklebust wrote:

> On Wed, 2025-05-14 at 09:15 -0400, Benjamin Coddington wrote:
>> Hey Trond and Anna - this series looked ready to go, but seems to
>> have never gotten upstream.  Was there a problem that needed work?
>>
>> I'd like to rebase these and submit them, but will hold off if its a
>> non-starter..
>>
>
> I believe the main issue raised at the time when we submitted all these
> attributes was that we had the ioctl() to retrieve and set them. The
> request from the community was that we use statx() to retrieve, and
> then add a new system call to set them.
>
> btime already has support in statx(), so there was relatively little
> work needed to convert these patches to use it.
>
> However for the other attributes (Windows Hidden, System, Archive
> attributes and the backup time) the main issue was adding the new
> system call to set them all. That work is yet to be done due to lack of
> developer time.
>
> If you have time to revive these patches and push the btime changes
> upstream, then that would be very welcome from our perspective. I'm
> happy to help in any capacity that I can.

Great news!  I did rebase and post just the btime portion, it needs a v2 so
I'll work on moving it along.

Ben


      parent reply	other threads:[~2025-05-28  0:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27 19:04 [PATCH v2 0/8] Support btime and other NFSv4 specific attributes trondmy
2021-12-27 19:04 ` [PATCH v2 1/8] NFS: Expand the type of nfs_fattr->valid trondmy
2021-12-27 19:04   ` [PATCH v2 2/8] nfs: Add timecreate to nfs inode trondmy
2021-12-27 19:04     ` [PATCH v2 3/8] NFS: Return the file btime in the statx results when appropriate trondmy
2021-12-27 19:05       ` [PATCH v2 4/8] nfs: Add 'archive', 'hidden' and 'system' fields to nfs inode trondmy
2021-12-27 19:05         ` [PATCH v2 5/8] nfs: Add 'time backup' " trondmy
2021-12-27 19:05           ` [PATCH v2 6/8] NFSv4: Support the offline bit trondmy
2021-12-27 19:05             ` [PATCH v2 7/8] NFS: Support statx_get and statx_set ioctls trondmy
2021-12-27 19:05               ` [PATCH v2 8/8] NFSv4: Add an ioctl to allow retrieval of the NFS raw ACCESS mask trondmy
2022-01-07 14:23             ` [PATCH v2 6/8] NFSv4: Support the offline bit Anna Schumaker
2022-01-07 14:26               ` Trond Myklebust
2022-01-07 14:31               ` Anna Schumaker
2022-01-07 14:36                 ` Trond Myklebust
2022-01-07 20:36                   ` Anna Schumaker
2025-05-14 13:15 ` [PATCH v2 0/8] Support btime and other NFSv4 specific attributes Benjamin Coddington
     [not found]   ` <cb113c0832d61ddddde7f01b3b78eb877a1f8cc5.camel@kernel.org>
2025-05-28  0:08     ` Benjamin Coddington [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=1C356965-867D-48B2-BAB1-C63FD6533CE0@redhat.com \
    --to=bcodding@redhat.com \
    --cc=anna@kernel.org \
    --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