From: Christoph Hellwig <hch@infradead.org>
To: Dan Carpenter <dan.carpenter@oracle.com>
Cc: richard.sharpe@primarydata.com, linux-nfs@vger.kernel.org,
lance.shelton@hammerspace.com, trond.myklebust@hammerspace.com,
Anna.Schumaker@netapp.com, linux-fsdevel@vger.kernel.org
Subject: Re: [bug report] NFS: Support statx_get and statx_set ioctls
Date: Tue, 11 Jan 2022 00:48:14 -0800 [thread overview]
Message-ID: <Yd1ETmx/HCigOrzl@infradead.org> (raw)
In-Reply-To: <20220111074309.GA12918@kili>
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.
next parent reply other threads:[~2022-01-11 8:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220111074309.GA12918@kili>
2022-01-11 8:48 ` Christoph Hellwig [this message]
2022-01-11 10:48 ` [bug report] NFS: Support statx_get and statx_set ioctls Christian Brauner
2022-01-11 18:08 ` Trond Myklebust
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=Yd1ETmx/HCigOrzl@infradead.org \
--to=hch@infradead.org \
--cc=Anna.Schumaker@netapp.com \
--cc=dan.carpenter@oracle.com \
--cc=lance.shelton@hammerspace.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=richard.sharpe@primarydata.com \
--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 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).