From: Christoph Hellwig <hch@infradead.org>
To: Ted Ts'o <tytso@mit.edu>
Cc: Lukas Czerner <lczerner@redhat.com>,
Curt Wohlgemuth <curtw@google.com>,
Ric Wheeler <rwheeler@redhat.com>,
Andreas Dilger <adilger@dilger.ca>,
linux-ext4 List <linux-ext4@vger.kernel.org>,
Jan Kara <jack@suse.cz>, Eric Sandeen <sandeen@redhat.com>
Subject: Re: [PATCH v2] ext4: Deprecate data=journal mount option
Date: Fri, 12 Aug 2011 16:57:19 -0400 [thread overview]
Message-ID: <20110812205719.GA1670@infradead.org> (raw)
In-Reply-To: <20110812181330.GG31181@thunk.org>
On Fri, Aug 12, 2011 at 02:13:30PM -0400, Ted Ts'o wrote:
> I have a rather long list of expected failures, mostly having to do
> with xfstests assuming that O_DIRECT has to be supported. On my todo
> list is to scrub through the list failures that I've seen, make sure
> they are indeed related to O_DIRECT, and then see if I can figure out
> some way of telling xfstests to skip O_DIRECT tests via some
> environment variable or command line option.
If you do it please do it by returning a defined failure from the
test programs and then just exiting the test with _notrun. But given
that xfstests does a lot of O_DIRECT testing it might be quite involved.
To be honest I'd expect a Linux filesystem without O_DIRECT not working
overly well in practical setup - it's pretty widely used these days.
A better fix might be simply accept O_DIRECT for data=journal, but
use the pagecache with a use once hint.
> BTW, with the very latest xfstests, I'm seeing new across-the-board
> (not just data=journal) failures for tests #62 (caused by the presence
> of the lost+found directory
062 fails because Andreas changed the error returns from the xattr
calls. He sent me a patch to accept the new errors, but I'm still
undecided wether the new ones are correct enough. I'll wait another
kernel release to see if real users complain about the change, and
will apply it then.
> and differences in error code returns for
> xattrs) and #79 (a failure in the append-only handling which I don't
> completely understand yet).
This was discussed on fsdevel lately. All filesystem but xfs inherit
the append only bit from directories to files created inside them.
This not only is not very useful behaviour, but also exposes a bug
in the vfs that allows to create these new files, but fail the open
unless using O_APPEND which is against the posix create semantics.
We'll have to either adopt the oether filesystems to the xfs semantics,
or adopt xfs to the common dumb semantics and fix that O_CREAT bug.
next prev parent reply other threads:[~2011-08-12 20:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 11:26 [PATCH v2] ext4: Deprecate data=journal mount option Lukas Czerner
2011-06-29 4:49 ` Bruce Guenter
2011-06-29 11:49 ` Lukas Czerner
2011-08-11 15:01 ` Lukas Czerner
2011-08-11 21:08 ` Andreas Dilger
2011-08-12 8:16 ` Lukas Czerner
2011-08-12 8:25 ` Ric Wheeler
2011-08-12 15:45 ` Curt Wohlgemuth
2011-08-12 16:08 ` Lukas Czerner
2011-08-12 18:13 ` Ted Ts'o
2011-08-12 20:57 ` Christoph Hellwig [this message]
2011-08-14 2:06 ` Ted Ts'o
2011-08-14 2:28 ` [PATCH] ext2,ext3,ext4: don't inherit APPEND_FL or IMMUTABLE_FL for new inodes Theodore Ts'o
2011-12-22 18:06 ` Eric Sandeen
2011-12-22 18:19 ` Ted Ts'o
2011-12-22 18:23 ` Eric Sandeen
2011-08-15 11:19 ` [PATCH v2] ext4: Deprecate data=journal mount option Jan Kara
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=20110812205719.GA1670@infradead.org \
--to=hch@infradead.org \
--cc=adilger@dilger.ca \
--cc=curtw@google.com \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=sandeen@redhat.com \
--cc=tytso@mit.edu \
/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).