From: Fabian Frederick <fabf@skynet.be>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-kernel@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jan Kara <jack@suse.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/1 linux-next] ext4: add compatibility flag check
Date: Fri, 25 Nov 2016 07:14:33 +0100 (CET) [thread overview]
Message-ID: <729028918.362386.1480054473313.open-xchange@webmail.nmp.proximus.be> (raw)
In-Reply-To: <20161125052639.3v56ef3clt7r52hr@thunk.org>
> On 25 November 2016 at 06:26 Theodore Ts'o <tytso@mit.edu> wrote:
>
>
> On Thu, Nov 24, 2016 at 08:47:41PM +0100, Fabian Frederick wrote:
> > data=journal mount option should disable O_DIRECT access
> > (See Documentation/filesystems/ext4.txt) but open operations
> > using O_CREAT|O_RDWR|O_DIRECT|O_SYNC have no warning in return and file is
> > being
> > created. This patch adds vfs super_operations compatibility flag function
> > returning -EPERM in such a case.
> >
> > Signed-off-by: Fabian Frederick <fabf@skynet.be>
>
> The general practice by most file systems in Linux (for better or for
> worse) is to silently fall back to buffered I/O instead of failing the
> O_DIRECT open. Feel free to try to convince linux-fsdevel otherwise,
> but that is the general and historical consensus of Linux file system
> developers.
>
> Cheers,
Thanks a lot Ted, I'll have a closer look at vfs/ext4 documentation and add some
details if required.
Regards,
Fabian
>
> - Ted
prev parent reply other threads:[~2016-11-25 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 19:47 [PATCH 1/1 linux-next] ext4: add compatibility flag check Fabian Frederick
2016-11-24 20:39 ` Al Viro
2016-11-24 21:43 ` Fabian Frederick
2016-11-25 5:26 ` Theodore Ts'o
2016-11-25 6:14 ` Fabian Frederick [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=729028918.362386.1480054473313.open-xchange@webmail.nmp.proximus.be \
--to=fabf@skynet.be \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--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).