Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Wed, 12 Jan 2022 00:06:38 -0800
From:   "hch@infradead.org" <hch@infradead.org>
To:     Trond Myklebust <trondmy@hammerspace.com>
Cc:     "dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
        "hch@infradead.org" <hch@infradead.org>,
        "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
        Lance Shelton <Lance.Shelton@hammerspace.com>,
        Richard Sharpe <Richard.Sharpe@hammerspace.com>,
        "Anna.Schumaker@netapp.com" <Anna.Schumaker@netapp.com>,
        "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [bug report] NFS: Support statx_get and statx_set ioctls
Message-ID: <Yd6MDkMJaU0ACMEH@infradead.org>
References: <20220111074309.GA12918@kili>
 <Yd1ETmx/HCigOrzl@infradead.org>
 <56202063c1eba6020b356a393178b9626652198e.camel@hammerspace.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <56202063c1eba6020b356a393178b9626652198e.camel@hammerspace.com>
Precedence: bulk

On Tue, Jan 11, 2022 at 06:08:27PM +0000, Trond Myklebust wrote:
> So firstly, there already has been a discussion of this on linux-
> fsdevel (and linux-kernel):
> https://lore.kernel.org/lkml/20160429125813.23636.49830.stgit@warthog.procyon.org.uk/
> and the consensus at the time was that these attributes were not needed
> in statx.

And apparently someone now has a different opinion, so we should restart
it.

> 
> The other issue is that this is not a duplicate of stat. It's adding
> support for both _setting_ and reading back these attributes. The
> ability to supporting reading the archive bit / backup time, for
> example, is completely useless unless you can also set those values
> after backing up the file. Right now, there is no support in the VFS
> for setting any attributes that are not part of the standard POSIX set.

Either way this has no business being private in NFS.  We need to
come to an agreement to have a proper interface for CIFS, fat, exfat
and the 2 ntfs drivers as welŀ.  With the first three being the most
important ones.

So big fat nack for stashing something like this into nfs without proper
review and coordination.