From: Christoph Hellwig <hch@infradead.org>
To: P??draig Brady <P@draigBrady.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
aneesh.kumar@linux.vnet.ibm.com,
"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Subject: Re: RFC: More functions allowed with O_PATH
Date: Tue, 27 Jan 2015 09:30:45 -0800 [thread overview]
Message-ID: <20150127173045.GA21651@infradead.org> (raw)
In-Reply-To: <54C78B8F.9090903@draigBrady.com>
On Tue, Jan 27, 2015 at 12:58:55PM +0000, P??draig Brady wrote:
> Since fsync(), fdatasync(), syncfs() work on an identifying descriptor,
> and all work against a read-only file for example,
> should any/all these functions work with a descriptor opened with O_PATH ?
fsync and fdatasync work on the file data, so they defintively
shouldn't.
syncfs might make sense as we just use it as a handle for the containing
filesystem.
Adding fchmod and fchown would be more useful as they are allowed by
Posix on O_EXEC and O_SEARCH fds.
prev parent reply other threads:[~2015-01-27 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 12:58 RFC: More functions allowed with O_PATH Pádraig Brady
2015-01-27 17:30 ` Christoph Hellwig [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=20150127173045.GA21651@infradead.org \
--to=hch@infradead.org \
--cc=P@draigBrady.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.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