From: "hch@lst.de" <hch@lst.de>
To: "Fu, Rodney" <rfu@panasas.com>
Cc: "hch@lst.de" <hch@lst.de>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: Provision for filesystem specific open flags
Date: Fri, 10 Nov 2017 18:23:44 +0100 [thread overview]
Message-ID: <20171110172344.GA15288@lst.de> (raw)
In-Reply-To: <BN3PR0801MB2257E7D90F26A85C1D16730EAB540@BN3PR0801MB2257.namprd08.prod.outlook.com>
On Fri, Nov 10, 2017 at 04:49:33PM +0000, Fu, Rodney wrote:
> The kernel prevents unknown open flags from being passed through to the
> underlying filesystem. I am wondering if people would be for or against the
> idea of provisioning some number of bits in the open flags that are opaque to
> the VFS layer but get passed down to the underlying filesystem? The motivation
> would be to allow filesystem specific semantics to be controllable via open,
> much like the more generic and pre-existing open flags.
Absolutely against. Open flags need to be defined in common code or
you are in a massive world of trouble.
next prev parent reply other threads:[~2017-11-10 17:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-10 16:49 Provision for filesystem specific open flags Fu, Rodney
2017-11-10 17:23 ` hch [this message]
2017-11-10 17:39 ` Fu, Rodney
2017-11-10 19:29 ` Matthew Wilcox
2017-11-10 21:04 ` Fu, Rodney
2017-11-11 0:37 ` Matthew Wilcox
2017-11-13 15:16 ` Fu, Rodney
2017-11-20 13:38 ` Jeff Layton
2017-11-13 0:48 ` Dave Chinner
2017-11-13 17:02 ` Fu, Rodney
2017-11-13 21:58 ` Dave Chinner
2017-11-14 17:35 ` Fu, Rodney
2017-11-20 13:53 ` Jeff Layton
2017-12-04 5:29 ` NeilBrown
2017-12-05 21:36 ` Andreas Dilger
2017-11-13 17:45 ` Bernd Schubert
2017-11-13 20:19 ` Fu, Rodney
2017-11-20 14:03 ` Florian Weimer
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=20171110172344.GA15288@lst.de \
--to=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=rfu@panasas.com \
--cc=viro@zeniv.linux.org.uk \
/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).