linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "dan.carpenter@oracle.com" <dan.carpenter@oracle.com>,
	"hch@infradead.org" <hch@infradead.org>
Cc: "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
Date: Tue, 11 Jan 2022 18:08:27 +0000	[thread overview]
Message-ID: <56202063c1eba6020b356a393178b9626652198e.camel@hammerspace.com> (raw)
In-Reply-To: <Yd1ETmx/HCigOrzl@infradead.org>

On Tue, 2022-01-11 at 00:48 -0800, Christoph Hellwig wrote:
> On Tue, Jan 11, 2022 at 10:43:09AM +0300, Dan Carpenter wrote:
> > Hello Richard Sharpe,
> > 
> > This is a semi-automatic email about new static checker warnings.
> > 
> > The patch bc66f6805766: "NFS: Support statx_get and statx_set
> > ioctls" 
> > from Dec 27, 2021, leads to the following Smatch complaint:
> 
> Yikes, how did that crap get merged?  Why the f**k does a remote file
> system need to duplicate stat?  This kind of stuff needs a proper
> discussion on linux-fsdevel.
> 
> And btw, the commit message is utter nonsense.

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.

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.

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  parent reply	other threads:[~2022-01-11 18:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220111074309.GA12918@kili>
2022-01-11  8:48 ` [bug report] NFS: Support statx_get and statx_set ioctls Christoph Hellwig
2022-01-11 10:48   ` Christian Brauner
2022-01-11 18:08   ` Trond Myklebust [this message]
2022-01-12  8:06     ` hch
2022-01-12  7:57   ` Amir Goldstein
2022-01-12 17:43     ` Darrick J. Wong
2022-01-13  3:52       ` Amir Goldstein
2022-01-13  6:30         ` Jeremy Allison
2022-01-13 14:58           ` Trond Myklebust
2022-01-13 17:50             ` Jeremy Allison
2022-01-13 15:01     ` Trond Myklebust

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=56202063c1eba6020b356a393178b9626652198e.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=Anna.Schumaker@netapp.com \
    --cc=Lance.Shelton@hammerspace.com \
    --cc=Richard.Sharpe@hammerspace.com \
    --cc=dan.carpenter@oracle.com \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@vger.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).