From: Matthew Wilcox <willy@infradead.org>
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 11:29:02 -0800 [thread overview]
Message-ID: <20171110192902.GA10339@bombadil.infradead.org> (raw)
In-Reply-To: <BN3PR0801MB2257E71C2A12EA41C77FF7EBAB540@BN3PR0801MB2257.namprd08.prod.outlook.com>
On Fri, Nov 10, 2017 at 05:39:21PM +0000, Fu, Rodney wrote:
> > Absolutely against. Open flags need to be defined in common code or you are in a massive world of trouble.
>
> I'm suggesting this can be done with definitions in common code via generically named open flags. Say for example if there was defined an O_FS1, O_FS2 (someone pick a better name) exposed for an application to use that has no meaning to the VFS layer, but could be interpreted by the filesystem. Could that work?
No. If you want new flags bits, make a public proposal. Maybe some
other filesystem would also benefit from them.
next prev parent reply other threads:[~2017-11-10 19:29 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
2017-11-10 17:39 ` Fu, Rodney
2017-11-10 19:29 ` Matthew Wilcox [this message]
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=20171110192902.GA10339@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=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).