From: Christoph Hellwig <hch@infradead.org>
To: Lukas Czerner <lczerner@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-xfs@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH 4/7] xfs: Implement fallocate query support mode
Date: Mon, 18 Sep 2017 10:56:51 -0700 [thread overview]
Message-ID: <20170918175651.GA7937@infradead.org> (raw)
In-Reply-To: <1505749947-26360-5-git-send-email-lczerner@redhat.com>
This seems to miss any explanation and 6 out of 7 patches.
That being said, I really detest adding weird query modes to random
syscalls. We should expose capabilities through the interface that
was designed for such things: (f)pathconf, as there are a lot more
important parameters we currently fail to expose to userspace to
start with.
next parent reply other threads:[~2017-09-18 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1505749947-26360-1-git-send-email-lczerner@redhat.com>
[not found] ` <1505749947-26360-5-git-send-email-lczerner@redhat.com>
2017-09-18 17:56 ` Christoph Hellwig [this message]
2017-09-19 3:28 ` [PATCH 4/7] xfs: Implement fallocate query support mode OGAWA Hirofumi
2017-09-19 8:15 ` Lukas Czerner
2017-09-19 14:13 ` Christoph Hellwig
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=20170918175651.GA7937@infradead.org \
--to=hch@infradead.org \
--cc=lczerner@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@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).